I met some trouble in my ironic env:
1. I have two ironic compute nodes & two BM nodes
2. BM1 is controlled by node1, BM2 is controlled by node2
3. I boot an instance on BM1
4. Stop nova-compute service on node1
5. node2 doesn't take over BM1 although node1 is not available
What I expect is that when node1 id down node2 can take over BM1.
I met some trouble in my ironic env:
1. I have two ironic compute nodes & two BM nodes
2. BM1 is controlled by node1, BM2 is controlled by node2
3. I boot an instance on BM1
4. Stop nova-compute service on node1
5. node2 doesn't take over BM1 although node1 is not available
What I expect is that when node1 id down node2 can take over BM1.
nova version: nova-common- 14.0.3- 9.el7ost. noarch nova-novncproxy -14.0.3- 9.el7ost. noarch nova-scheduler- 14.0.3- 9.el7ost. noarch novaclient- 6.0.0-1. el7ost. noarch nova-conductor- 14.0.3- 9.el7ost. noarch nova-api- 14.0.3- 9.el7ost. noarch nova-14. 0.3-9.el7ost. noarch nova-cert- 14.0.3- 9.el7ost. noarch nova-console- 14.0.3- 9.el7ost. noarch nova-compute- 14.0.3- 9.el7ost. noarch nova-common- 14.0.3- 9.el7ost. noarch
openstack-
openstack-
openstack-
python-
openstack-
openstack-
python-
openstack-
openstack-
openstack-
openstack-