Decommission a Machine
Changed onStart decommissioning a Machine. The Machine must be in Core's Ready state, and every attached DPU must support BFB installation through Redfish. The operation is asynchronous; use the Machine status to observe workflow progress.
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.
Request
- Base URLhttps://nico-rest-api.nico.svc.cluster.local
- URLhttps://nico-rest-api.nico.svc.cluster.local/v2/org/{org}/nico/machine/{machineId}/decommission
- AuthHTTP bearer
Response
Machine decommissioning was accepted and will proceed asynchronously.
Example response
{
"message": "Deletion request was accepted"
}Changes
- info
removed the
nicoenum value from theresponse property for the response status - info
removed the
nicoenum value from theresponse property for the response status - info
removed the
nicoenum value from theresponse property for the response status - info
removed the
nicoenum value from theresponse property for the response status - info
removed the
nicoenum value from theresponse property for the response status - info
removed the
nicoenum value from theresponse property for the response status - info
removed the
nicoenum value from theresponse property for the response status
- info
- info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status
- info