yahoo-eng-team team mailing list archive

[Balazs Gibizer <1896574@xxxxxxxxxxxxxxxxxx>]

The hypervisor host name is the compute node identity so if you change the hostname you basically introduce a new compute node into the system while you silently remove the old one from the system. If you have to change the hostname the do it the following way:
1) disable the compute node
2) drain the instances from the compute node by live migrating them
3) stop the nova-compute service on the compute host
4) delete the compute service from openstack 
5) change the hostname of the compute host
6) start the nova-compute service

Setting this bug as Invalid. Please set it back to New if you have
further questions.

** Changed in: nova
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1896574

Title:
  how to deal with hypervisor name changing

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  nova fails to correctly account for resources after hypervisor name
  changes. For example, if previously the hypervisor name is A, and some
  later it switches to A.B, then all of the instances which belong to A
  will not be included in the resource computation for A.B although
  effectively they are the same thing.

  Is there any way to deal with this situation? we are using openstack
  rocky.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1896574/+subscriptions