Chapter 11. 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 and openstack-ironic-conductor. Likewise, ironic-inspector uses two units as well: openstack-ironic-inspector and openstack-ironic-inspector-dnsmasq. Use both units for each respective component. For example: 
    $ sudo journalctl -u openstack-ironic-inspector -u openstack-ironic-inspector-dnsmasq
  • ironic-inspector also stores the ramdisk logs in /var/log/ironic-inspector/ramdisk/ as gz-compressed tar files. Filenames contain date, time, and the IPMI address of the node. Use these logs for diagnosing introspection issues.

11.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 11.1. Fixing an Incorrect MAC Address

  1. Find out the assigned port UUID: 
    $ ironic node-port-list [NODE UUID]
  2. Update the MAC address: 
    $ ironic port-update [PORT UUID] replace address=[NEW MAC]

Procedure 11.2. Fix an Incorrect IPMI Address

  • Run the following command: 
    $ ironic node-update [NODE UUID] replace driver_info/ipmi_address=[NEW IPMI ADDRESS]