Description of problem: Node cannot reboot, is stuck in reboot mode Version-Release number of selected component (if applicable): Build 2018-04-19.2 openstack-nova-api-17.0.3-0.20180413225830.fda768b.el7ost.noarch openstack-nova-conductor-17.0.3-0.20180413225830.fda768b.el7ost.noarch python-novaclient-9.1.1-1.el7ost.noarch openstack-nova-placement-api-17.0.3-0.20180413225830.fda768b.el7ost.noarch openstack-nova-compute-17.0.3-0.20180413225830.fda768b.el7ost.noarch python-nova-17.0.3-0.20180413225830.fda768b.el7ost.noarch puppet-nova-12.4.1-0.20180413152104.a054a18.el7ost.noarch openstack-nova-common-17.0.3-0.20180413225830.fda768b.el7ost.noarch openstack-nova-scheduler-17.0.3-0.20180413225830.fda768b.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Deploy overcloud 2. nova reboot <controller node> or openstack server reboot <controller node> 3. Actual results: Node is stuck in state "REBOOT", si not accessible from ssh. Have to reboot it from Machine Manager Expected results: Reboot is performed silently Additional info:
Hi, I have tried to reproduce the issue by mentioned steps, but as expected the controller node comes to ACTIVE state in some time, after REBOOT. Could you please try it on fresh deployment and check whether it is reproducible or not ?
Doesn't happen anymore on the fresh puddle from 2018-05-03.2