yahoo-eng-team team mailing list archive

[Dmitriy Rabotyagov <2033209@xxxxxxxxxxxxxxxxxx>]

Hey,

Sorry, I am inclined to say that the problem you are describing is
specifically nova issue. I will change affected project to Nova, as I
believe this bug report fits better there.

As far as I know regarding the topic - this is pretty much intended
behavior and a known dropback. The only workaround I'm aware of is to
update the database. So in case a hostname for compute needs to change,
we always ensure that no VM is running there before doing so.

** Project changed: openstack-ansible => nova

-- 
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):
  New

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