openstack/ironic-inspector
Code Issues Proposed changes

[doc] Add misconfigured BMC channel to trouble shooting guide

Browse Source 
Change-Id: I7285528511fd9cecd428a3a502281b4bd84dcd82
This commit is contained in:
Arne Wiebalck 2020-06-05 09:04:10 +02:00
parent 3a9e117aad
commit 6175bc4f5f
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/source/user/troubleshooting.rst
View File

@ -46,6 +46,17 @@ option is set, **ironic-inspector** will store logs received from the ramdisk
to the ``ramdisk_logs_dir`` directory. This depends, however, on the ramdisk to the ``ramdisk_logs_dir`` directory. This depends, however, on the ramdisk
implementation. implementation.
A local cache miss during data processing would leave a message like:
.. code-block:: bash
ERROR ironic_python_agent.inspector [-] inspectorerror 400: {"error":{"message":"The following failures happened during running pre-processing hooks:\nLook up error: Could not find a node for attributes {'bmc_address': u'10.x.y.z', 'mac': [u'00:aa:bb:cc:dd:ee', u'00:aa:bb:cc:dd:ef']}"}}
One potential explanation for such an error is a misconfiguration in the BMC
where a channel with the wrong IP address is active (and hence detected and
reported back by the Ironic Python Agent), but can then not be matched to the
IP address Ironic has in its cache for this node.
Troubleshooting PXE boot Troubleshooting PXE boot
^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^