When this kind of very corner case happen I usually hack manually the database. Go with mysql in the nova database and put the new ID for those two instances.
my 2 cents Saverio 2016-03-23 5:17 GMT+01:00 Rahul Sharma <rahulsharma...@gmail.com>: > Hi All, > > Due to a hostname change, we ended up having a new hypervisor-id for one of > our compute nodes. It was already running two instances and then, we didn't > catch the updated hypervisor-id. This ended up with new instances spawning > up with new hypervisor-id. > > Now, the instances with older hypervisor-id are not seen in "virsh list", > rebooting those instances keep them rebooting. > > [root (admin)]# nova hypervisor-servers compute-90 > +--------------------------------------+-------------------+---------------+---------------------+ > | ID | Name | Hypervisor ID | > Hypervisor Hostname | > +--------------------------------------+-------------------+---------------+---------------------+ > | 9688dcef-2836-496f-8b70-099638b73096 | instance-00000712 | 40 | > compute-90.test.edu | > | f7373cd6-96a0-4643-9137-732ea5353e94 | instance-00000b74 | 40 | > compute-90.test.edu | > | c8926585-a260-45cd-b008-71df2124b364 | instance-00001270 | 92 | > compute-90.test.edu | > | a0aa3f5f-d49b-43a6-8465-e7865bb68d57 | instance-000018de | 92 | > compute-90.test.edu | > | d729f9f4-fcae-4abe-803c-e9474e533a3b | instance-000016e0 | 92 | > compute-90.test.edu | > | 30a6a05d-a170-4105-9987-07a875152907 | instance-000017e4 | 92 | > compute-90.test.edu | > | 6e0fa25b-569d-4e9e-b57d-4c182c1c23ea | instance-000018f8 | 92 | > compute-90.test.edu | > | 5964f6cc-eec3-493a-81fe-7fb616c89a8f | instance-000018fa | 92 | > compute-90.test.edu | > +--------------------------------------+-------------------+---------------+---------------------+ > > [root@compute-90]# virsh list > Id Name State > ---------------------------------------------------- > 112 instance-00001270 running > 207 instance-000018de running > 178 instance-000016e0 running > 189 instance-000017e4 running > 325 instance-000018f8 running > 336 instance-000018fa running > > Instances not visible: instance-00000712 and instance-00000b74 > > Is there a way to recover from this step? I can delete the old services(nova > service-delete <id>), but I am confused whether it will lead to loss of > already running instances with old hypervisor-id? Is there a way I can > update the state of those instances to use hypervisor-id as 92 instead of > 40? Kindly do let me know if you have any suggestions. > > Thanks. > > Rahul Sharma > MS in Computer Science, 2016 > College of Computer and Information Science, Northeastern University > Mobile: 801-706-7860 > Email: rahulsharma...@gmail.com > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > _______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators