yahoo-eng-team team mailing list archive

[Jimmy McCrory <2049120@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Our hypervisors were all originally registered with their short names.

After upgrading to 2023.1, it looks like nova-compute now relies on
libvirt, which provides an FQDN, for the hosts' names and the service
fails to start with this error:

Error starting thread.: nova.exception.InvalidConfiguration: My compute
node f5507be0-83a7-4ad3-b723-f62fab368182 has hypervisor_hostname
shortname but virt driver reports it should be shortname.domain.
Possible rename detected, refusing to start!

Is there any workaround for this or ability to rename existing
registered computes to their FQDNs?

** Affects: nova
     Importance: Undecided
         Status: New

-- 
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/2049120

Title:
  Unable to upgrade nova-compute to 2023.1 due to existing hostname

Status in OpenStack Compute (nova):
  New

Bug description:
  Our hypervisors were all originally registered with their short names.

  After upgrading to 2023.1, it looks like nova-compute now relies on
  libvirt, which provides an FQDN, for the hosts' names and the service
  fails to start with this error:

  Error starting thread.: nova.exception.InvalidConfiguration: My
  compute node f5507be0-83a7-4ad3-b723-f62fab368182 has
  hypervisor_hostname shortname but virt driver reports it should be
  shortname.domain. Possible rename detected, refusing to start!

  Is there any workaround for this or ability to rename existing
  registered computes to their FQDNs?

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