Chapter 12. Troubleshooting Director Issues
An error can occur at certain stages of the director's processes. This section provides some information for diagnosing common problems.
Note the common logs for the director's components:
- The
/var/log
directory contains logs for many common OpenStack Platform components as well as logs for standard Red Hat Enterprise Linux applications. - The
journald
service provides logs for various components. Note that Ironic uses two units:openstack-ironic-api
andopenstack-ironic-conductor
. Likewise,ironic-discoverd
uses two units as well:openstack-ironic-discoverd
andopenstack-ironic-discoverd-dnsmasq
. Use both units for each respective component. For example:sudo journalctl -u openstack-ironic-discoverd -u openstack-ironic-discoverd-dnsmasq
$ sudo journalctl -u openstack-ironic-discoverd -u openstack-ironic-discoverd-dnsmasq
Copy to Clipboard Copied! ironic-discoverd
also stores the ramdisk logs in/var/log/ironic-discoverd/ramdisk/
as gz-compressed tar files. Filenames contain date, time, and IPMI address of the node. Use these logs for diagnosing introspection issues.
12.1. Troubleshooting Node Registration
Issues with node registration usually arise from issues with incorrect node details. In this case, use
ironic
to fix problems with node data registered. Here are a few examples:
Procedure 12.1. Fixing an Incorrect MAC Address
- Find out the assigned port UUID:
ironic node-port-list [NODE UUID]
$ ironic node-port-list [NODE UUID]
Copy to Clipboard Copied! - Update the MAC address:
ironic port-update [PORT UUID] replace address=[NEW MAC]
$ ironic port-update [PORT UUID] replace address=[NEW MAC]
Copy to Clipboard Copied!
Procedure 12.2. Fix an Incorrect IPMI Address
- Run the following command:
ironic node-update [NODE UUID] replace driver_info/ipmi_address=[NEW IPMI ADDRESS]
$ ironic node-update [NODE UUID] replace driver_info/ipmi_address=[NEW IPMI ADDRESS]
Copy to Clipboard Copied!