Some hardware changes boot device ordering in an unexpected way when receiving an IPMI bootdev command. This may prevent nodes from booting from the correct NIC or prevent PXE from booting at all. This release introduces a new "noop" management interface for the "ipmi" driver. When it is used, bootdev commands are not issued, and the current boot order is used. Nodes must be configured to try PXE booting from the correct NIC, and then fall back to the local hard drive. This change ensures a pre-configured boot order is kept with the new management interface.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:3587
Verified: Environment: instack-undercloud-8.4.6-2.el7ost.noarch (undercloud) [stack@undercloud-0 ~]$ openstack baremetal node list -f value --fields name management_interface compute-0 noop controller-0 noop [root@sealusa5 ~]# virsh dumpxml controller-0|awk '/<os>/,/<\/os>/' <os> <type arch='x86_64' machine='pc-i440fx-rhel7.5.0'>hvm</type> <boot dev='network'/> <boot dev='hd'/> </os> [root@sealusa5 ~]# virsh dumpxml compute-0|awk '/<os>/,/<\/os>/' <os> <type arch='x86_64' machine='pc-i440fx-rhel7.5.0'>hvm</type> <boot dev='network'/> <boot dev='hd'/> </os> Successfully deployed OC: Stack overcloud CREATE_COMPLETE Host 10.0.0.103 not found in /home/stack/.ssh/known_hosts Started Mistral Workflow tripleo.deployment.v1.get_horizon_url. Execution ID: 30da7123-d3b0-4b13-b603-0f01375620dd Overcloud Endpoint: http://10.0.0.103:5000/ Overcloud Horizon Dashboard URL: http://10.0.0.103:80/dashboard Overcloud rc file: /home/stack/overcloudrc Overcloud Deployed