Reset Machine Chassis

PATCH

https://nico-rest-api.nico.svc.cluster.local/v2/org/:org/nico/machine/:machineId/chassis/:chassisId/reset

Queue a case-sensitive Redfish chassis reset on an unassigned Machine owned by the Provider Admin’s Org. The Machine must be present on a Registered Site and be a managed host in the Ready lifecycle state with operator maintenance enabled and no pending maintenance operation. The chassis ID is required; each request targets one chassis. A 202 response means queued, not completed; metadata.lifecycleState.value transitions through Maintenance(...) to Ready when the BMC accepts the reset, or Failed/... if dispatch fails. Ready does not confirm hardware recovery; verify recovery before clearing operator maintenance. Read the Machine with includeMetadata=true to inspect its lifecycle state. The reset sends the Redfish ForceRestart action to the selected chassis. The selected chassis must support the Redfish reset action. Pending reset work and operator maintenance block new allocations. Org must have an Infrastructure Provider entity and own the Site that the Machine belongs to. User must have authorization role with PROVIDER_ADMIN suffix.

Queue a case-sensitive Redfish chassis reset on an unassigned Machine owned by the Provider Admin's Org. The Machine must be present on a Registered Site and be a managed host in the `Ready` lifecycle state with operator maintenance enabled and no pending maintenance operation. The chassis ID is required; each request targets one chassis. A `202` response means queued, not completed; `metadata.lifecycleState.value` transitions through `Maintenance(...)` to `Ready` when the BMC accepts the reset, or `Failed/...` if dispatch fails. `Ready` does not confirm hardware recovery; verify recovery before clearing operator maintenance. Read the Machine with `includeMetadata=true` to inspect its lifecycle state. The reset sends the Redfish `ForceRestart` action to the selected chassis. The selected chassis must support the Redfish reset action. Pending reset work and operator maintenance block new allocations. Org must have an Infrastructure Provider entity and own the Site that the Machine belongs to. User must have authorization role with `PROVIDER_ADMIN` suffix.

Authentication

AuthorizationBearer

export JWT_BEARER_TOKEN="<jwt-bearer-token>"
# Example org name: "acme-inc
export ORG_NAME=<org-name>
# Use the JWT bearer token in your API request auth header:
curl -v -X GET -H "Content-Type: application/json" -H "Authorization: Bearer $JWT_BEARER_TOKEN" https://nico-rest-api.nico.svc.cluster.local/v2/org/$ORG_NAME/nico/user/current

``` export JWT_BEARER_TOKEN="<jwt-bearer-token>" # Example org name: "acme-inc export ORG_NAME=<org-name> # Use the JWT bearer token in your API request auth header: curl -v -X GET -H "Content-Type: application/json" -H "Authorization: Bearer $JWT_BEARER_TOKEN" https://nico-rest-api.nico.svc.cluster.local/v2/org/$ORG_NAME/nico/user/current ```

Path parameters

orgstringRequired

Name of the Org

machineIdstringRequired

ID of the Machine

chassisIdstringRequiredformat: "^[A-Za-z0-9_-][A-Za-z0-9._-]*$">=1 character

Case-sensitive Redfish chassis identifier for the single chassis to reset

Response

Machine chassis reset request was accepted

messagestring

Human-readable outcome of the request

Errors

400

Bad Request Error

403

Forbidden Error

404

Not Found Error

412

Precondition Failed Error

500

Internal Server Error