Mirantis Container Cloud (MCC) becomes part of Mirantis OpenStack for Kubernetes (MOSK)!

Starting with MOSK 25.2, the MOSK documentation set covers all product layers, including MOSK management (formerly Container Cloud). This means everything you need is in one place. Some legacy names may remain in the code and documentation and will be updated in future releases. The separate Container Cloud documentation site will be retired, so please update your bookmarks for continued easy access to the latest content.

Restart the inspection of a bare metal host¶

You can use the MOSK management API to restart an inspection of a bare metal host in MOSK clusters. For example, this procedure is useful when hardware was changed. This works for bare metal hosts that were not provisioned yet or were successfully deprovisioned.

The workflow of the reinspection procedure desribed above is as follows:

Ensure that the BareMetalHostInventory object is not bound to any Machine object and it is in the available state.
Edit the BareMetalHostInventory object to initiate an inspection of the bare metal server that hosts the node.

Note

Before update of the management cluster to 2.29.0 (Cluster release 16.4.0), instead of BareMetalHostInventory, use the BareMetalHost object. For details, see BareMetalHost resource.

Caution

While the Cluster release of the management cluster is 16.4.0, BareMetalHostInventory operations are allowed to m:kaas@management-admin only. This limitation is lifted once the management cluster is updated to the Cluster release 16.4.1 or later.

To restart the inspection of a bare metal host:

Using kubeconfig of the management cluster, access the MOSK management API and inspect the BareMetalHost object:

kubectl -n <project-name> get baremetalhost <bare-metal-host-name>

Example of the system response:

NAME                             STATE       CONSUMER                         ONLINE   ERROR   AGE
...
mosk-worker-a-storage-worker  preparing   mosk-worker-a-storage-worker  false            5d3h
mosk-worker-b-storage-worker  preparing   mosk-worker-b-storage-worker  false            5d3h
mosk-worker-c-storage-worker  available                                    false            5d3h

In the system response above, the mosk-worker-c-storage-worker bare metal host is in the available state and has no consumer (not bound to any Machine). Therefore, you can reinspect it.

Open the required bare metal host object for editing:
Since the management cluster update to 2.29.0
kubectl -n <project-name> edit baremetalhostinventory <host-name>
Before the management cluster update to 2.29.0
kubectl -n <project-name> edit baremetalhost <host-name>
Annotate the object with the inspect.metal3.io annotation and ensure that online equals true in the object spec:
```
metadata:
  annotations:
    ...
    inspect.metal3.io: ""
```
```
spec:
  ...
  online: true
```
Once you save changes, approximately in one minute, the state of the bare metal host changes to inspecting.

Verify the state of the bare metal host:

kubectl -n <project-name> get baremetalhost <host-name>

Example of a system response:

NAME                             STATE        CONSUMER    ONLINE   ERROR   AGE
mosk-worker-c-storage-worker  inspecting               true             5d3h