← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1907775] Re: After change Host's Availability Zone, the deployed VMs Availability Zone data(in novaapi.request_specs table) can not be updated

 

Reviewed:  https://review.opendev.org/c/openstack/nova/+/821423
Committed: https://opendev.org/openstack/nova/commit/3c0eadae0b9ec48586087ea6c0c4e9176f0aa3bc
Submitter: "Zuul (22348)"
Branch:    master

commit 3c0eadae0b9ec48586087ea6c0c4e9176f0aa3bc
Author: Balazs Gibizer <balazs.gibizer@xxxxxxxx>
Date:   Fri Dec 10 17:53:30 2021 +0100

    Reject AZ changes during aggregate add / remove host
    
    After this patch nova rejects the add host to aggregate API action
    if the host has instances and the new aggregate for the host would
    mean that these instances need to move from one AZ (even from the
    default one) to another. Such AZ change is not implemented in nova
    and currently leads to stuck instances.
    
    Similarly nova will reject remove host from aggregate API action if the
    host has instances and the aggregate removal would mean that the
    instances need to change AZ.
    
    Depends-On: https://review.opendev.org/c/openstack/tempest/+/821732
    
    Change-Id: I19c4c6d34aa2cc1f32d81e8c1a52762fa3a18580
    Closes-Bug: #1907775


** Changed in: nova
       Status: In Progress => Fix Released

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

Title:
  After change Host's Availability Zone, the deployed VMs Availability
  Zone data(in novaapi.request_specs table) can not be updated

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Description
  ===========

  After change Host's Availability Zone, the deployed VMs Availability
  Zone data(in request_specs table) can not be updated

  Steps to reproduce
  ==================
  1.Create host aggregates block_az, add two hosts into this host aggregates, also set availability_zone to block_az.
  2.Deploy a VM, named: rhel82-official-block-az
  3.Now remove 2 hosts from block_az host aggregates, these 2 hosts are in "Default_Group" AZ
  4. openstack server show rhel82-official-block-az, the availability_zone is correct
  +-------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------+
  | Field                               | Value                                                                                                                                |
  +-------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------+
  | OS-DCF:diskConfig                   | MANUAL                                                                                                                               |
  | OS-EXT-AZ:availability_zone         | Default_Group                                                                                                                        |
  | OS-EXT-SRV-ATTR:host                | kvmperf2.icic.boe                                                                                                                    |
  | OS-EXT-SRV-ATTR:hostname            | rhel82-official-block-az                                                                                                             |
  | OS-EXT-SRV-ATTR:hypervisor_hostname | kvmperf2.icic.boe

  5.From novaapi.request_specs table, the AZ is still the original
  "block_az" and is incorrect.

  MariaDB [novaapi]> select * from request_specs where
  instance_uuid='5f4c292b-30b4-4bce-b204-5304306248cb';

   "availability_zone": "block_az", "flavor": .....


  Expected result
  ===============
   "availability_zone" in novaapi.request_specs table can be updated when vm's host is changed.

  Actual result
  =============
   "availability_zone" in novaapi.request_specs table is updated when vm's host is changed.

  Environment
  ===========
  Ussuri release

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



References