yahoo-eng-team team mailing list archive

[Artom Lifshitz <2033209@xxxxxxxxxxxxxxxxxx>]

If I understand correctly, it looks like the hostnames of your compute
hosts has changed because of a deployment error. I understand that this
is not your fault, but renaming compute host names is essentially
forbidden, as it causes the kind of breakage that you're reporting in
this bug.

We have implemented protections from this in [1], but that work will
only be released in Caracal. I'm afraid for now hostnames are immutable,
and manual repair and recovery is needed if one of more compute hosts
get renamed.

[1] https://review.opendev.org/c/openstack/nova/+/872432

** 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/2033209

Title:
  changing openstack_domain does not change in nova DB

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  In inventory/group_vars/all.yml file and in
  openstack_hosts/defaults/main.yml role openstack_domain variable
  defined as openstack.local

  openstack_domain: openstack.local

  However, during OSA deployment for some reason, we used the FQDN name.
  such as example.com

  after updating the openstack_domain.
  all existing instances has error while live-migration that they can not find the new compute.

  Unable to find record for source node compute-02.openstack.local on compute-02:
  nova.exception.ComputeHostNotFound: Compute host compute-02 could not be found.

  it searched for compute-02.openstack.local but it does not exist anymore. After I checked the Nova DB
  I found that the compute_nodes and instances table is not updated with the new openstack_domain name.
  now I want  a way other than manually changing the DB fields

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