yahoo-eng-team team mailing list archive

[norman shen <1896574@xxxxxxxxxxxxxxxxxx>]

I think previous title is misleading. Actually hostname itself is still
A. what changes is fqdn name seen by hostname --fqdn.

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

** Summary changed:

- how to deal with hypervisor name changing
+ how to deal with hypervisor host fqdn name changing

** Description changed:

- 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
+ nova fails to correctly account for resources after hypervisor hosntame
+ fqdn changes. For example, if previously the hypervisor hostname fqdn is
+ A, and some later it 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.
  
+ But under such circumstances, compute service's is still A.
+ 
  Is there any way to deal with this situation? we are using openstack
  rocky.

** Description changed:

  nova fails to correctly account for resources after hypervisor hosntame
  fqdn changes. For example, if previously the hypervisor hostname fqdn is
  A, and some later it 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.
  
- But under such circumstances, compute service's is still A.
+ But under such circumstances, compute service's is listed as A.
  
  Is there any way to deal with this situation? we are using openstack
  rocky.

-- 
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 host fqdn name changing

Status in OpenStack Compute (nova):
  New

Bug description:
  nova fails to correctly account for resources after hypervisor
  hosntame fqdn changes. For example, if previously the hypervisor
  hostname fqdn is A, and some later it 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.

  But under such circumstances, compute service's is listed as A.

  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