Add troubleshooting BMO/Ironic healthy

Add section on how to verify that BMO and Ironic are healthy as well as
example output for both healthy and unhealthy examples.

Signed-off-by: Lennart Jern <[email protected]>

docs/user-guide/src/troubleshooting.md

@@ -1,5 +1,45 @@
 # Troubleshooting
 
+## Verify that Ironic and Baremetal Operator are healthy
+
+There is no point continuing before you have verified that the controllers are
+healthy. A "standard" deployment will have Ironic and Baremetal Operator running
+in the `baremetal-operator-system` namespace. Check that the containers are
+running, not restarting or crashing:
+
+```bash
+kubectl -n baremetal-operator-system get pods
+```
+
+Note: If you deploy Ironic outside of Kubernetes you will need to check on it in
+a different way.
+
+Healthy example output:
+
+```text
+NAME                                                     READY   STATUS    RESTARTS       AGE
+baremetal-operator-controller-manager-85b896f688-j27g5   1/1     Running   0              5m13s
+ironic-6bcdcb99f8-6ldlz                                  3/3     Running   1 (2m2s ago)   5m15s
+```
+
+(There has been one restart, but it is not constantly restarting.)
+
+Unhealthy example output:
+
+```text
+NAME                                                     READY   STATUS    RESTARTS      AGE
+baremetal-operator-controller-manager-85b896f688-j27g5   1/1     Running   0             3m35s
+ironic-6bcdcb99f8-6ldlz                                  1/3     Running   1 (24s ago)   3m37s
+```
+
+### Waiting for IP
+
+Make sure to check the logs also since Ironic may be stuck on "waiting for IP".
+
+```bash
+kubectl -n baremetal-operator-system logs deploy/ironic
+```
+
 ## Host is stuck in cleaning, how do I delete it?
 
 First and foremost, avoid using forced deletion, otherwise you'll have [a