12.2. Troubleshooting Hardware Introspection
ironic-discoverd) times out after a default 1 hour period if the discovery ramdisk provides no response. Sometimes this might indicate a bug in the discovery ramdisk but usually it happens due to environment misconfiguration, particularly BIOS boot settings.
Errors with Starting Node Introspection
baremetal introspection, which acts an an umbrella command for Ironic's services. However, if running the introspection directly with
ironic-discoverd, it might fail to discover nodes in the AVAILABLE state, which is meant for deployment and not for discovery. Change the node status to the MANAGEABLE state before discovery:
$ ironic node-set-provision-state [NODE UUID] manage
$ ironic node-set-provision-state [NODE UUID] provide
Stopping the Discovery Process
ironic-discoverddoes not provide a direct means for stopping discovery. The recommended path is to wait until the process times out. If necessary, change the
/etc/ironic-discoverd/discoverd.confto change the timeout period to another period in minutes.
Procedure 12.3. Stopping the Discovery Process
- Change the power state of each node to off:
$ ironic node-set-power-state [NODE UUID] off
ironic-discoverdcache and restart it:
$ rm /var/lib/ironic-discoverd/discoverd.sqlite $ sudo systemctl restart openstack-ironic-discoverd