1
1
# Troubleshooting
2
2
3
+ ## Verify that Ironic and Baremetal Operator are healthy
4
+
5
+ There is no point continuing before you have verified that the controllers are
6
+ healthy. A "standard" deployment will have Ironic and Baremetal Operator running
7
+ in the ` baremetal-operator-system ` namespace. Check that the containers are
8
+ running, not restarting or crashing:
9
+
10
+ ``` bash
11
+ kubectl -n baremetal-operator-system get pods
12
+ ```
13
+
14
+ Note: If you deploy Ironic outside of Kubernetes you will need to check on it in
15
+ a different way.
16
+
17
+ Healthy example output:
18
+
19
+ ``` text
20
+ NAME READY STATUS RESTARTS AGE
21
+ baremetal-operator-controller-manager-85b896f688-j27g5 1/1 Running 0 5m13s
22
+ ironic-6bcdcb99f8-6ldlz 3/3 Running 1 (2m2s ago) 5m15s
23
+ ```
24
+
25
+ (There has been one restart, but it is not constantly restarting.)
26
+
27
+ Unhealthy example output:
28
+
29
+ ``` text
30
+ NAME READY STATUS RESTARTS AGE
31
+ baremetal-operator-controller-manager-85b896f688-j27g5 1/1 Running 0 3m35s
32
+ ironic-6bcdcb99f8-6ldlz 1/3 Running 1 (24s ago) 3m37s
33
+ ```
34
+
35
+ ### Waiting for IP
36
+
37
+ Make sure to check the logs also since Ironic may be stuck on "waiting for IP".
38
+
39
+ ``` bash
40
+ kubectl -n baremetal-operator-system logs deploy/ironic
41
+ ```
42
+
3
43
## Host is stuck in cleaning, how do I delete it?
4
44
5
45
First and foremost, avoid using forced deletion, otherwise you'll have [ a
@@ -18,7 +58,7 @@ it does not finish.
18
58
19
59
## MAC address conflict on registration
20
60
21
- If you force deletion of a host after registration, BareMetal Operator will not
61
+ If you force deletion of a host after registration, Baremetal Operator will not
22
62
be able to delete the corresponding record from Ironic. If you try to enroll
23
63
the same host again, you will see the following error:
24
64
0 commit comments