X-Git-Url: https://gerrit.akraino.org/r/gitweb?a=blobdiff_plain;f=doc%2Ftroubleshooting.md;h=198118644885eec8e1a67d7fd81ef96e2adf6278;hb=refs%2Fchanges%2F07%2F4707%2F1;hp=6dc0011d4c694cbc0a2f3f1eb59af587b873b12f;hpb=641f56a07791b0a3eabd23c0a0696b7aa0cb675c;p=icn.git

diff --git a/doc/troubleshooting.md b/doc/troubleshooting.md
index 6dc0011..1981186 100644
--- a/doc/troubleshooting.md
+++ b/doc/troubleshooting.md
@@ -27,6 +27,10 @@ Examining the BareMetalHost resource of the failing machine and the
 logs of Bare Metal Operator and Ironic Pods may also provide a
 description of why the provisioning is failing.
 
+A description of the BareMetalHost states can be found in the [Bare
+Metal Operator
+documentation](https://github.com/metal3-io/baremetal-operator/blob/main/docs/baremetalhost-states.md).
+
 ### openstack baremetal
 
 In rare cases, the Ironic and Bare Metal Operator information may get
@@ -115,3 +119,18 @@ this, Flux will complete reconcilation succesfully.
 Provisioning can take a fair amount of time, refer to [Monitoring
 progress](installation-guide.md#monitoring-progress) to see where the
 process is.
+
+A description of the BareMetalHost states can be found in the [Bare
+Metal Operator
+documentation](https://github.com/metal3-io/baremetal-operator/blob/main/docs/baremetalhost-states.md).
+
+## Vagrant destroy fails with `cannot undefine domain with nvram`
+
+The fix is to destroy each machine individually.  For the default ICN
+virtual machine deployment:
+
+    vagrant destroy -f jump
+    virsh -c qemu:///system destroy vm-machine-1
+    virsh -c qemu:///system undefine --nvram --remove-all-storage vm-machine-1
+    virsh -c qemu:///system destroy vm-machine-2
+    virsh -c qemu:///system undefine --nvram --remove-all-storage vm-machine-2