yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #84750
[Bug 1907775] [NEW] After change Host's Availability Zone, the deployed VMs Availability Zone data(in novaapi.request_specs table) can not be updated
Public bug reported:
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
** Affects: nova
Importance: Undecided
Status: New
** Summary changed:
- After change Host's Availability Zone, the deployed VMs Availability Zone data(in request_specs table) can not be updated
+ After change Host's Availability Zone, the deployed VMs Availability Zone data(in novaapi.request_specs table) can not be updated
--
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):
New
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
Follow ups