Fail to filter the list of instances by availability zone
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
In Progress
|
Medium
|
huanhongda |
Bug Description
After the host is in the Host Aggregates (HA) where the host is modified, the Availability Zone (az) is also changed, but the available_zone in the instances database of the instance on the host does not change.
The recurring steps are as follows:
1. Query the az of the instance by nova-api:
[root@node01 ~]# nova show 82d28856-
| OS-EXT-
| OS-EXT-
2. In the database use sql to query the current instance of az:
MariaDB [nova_cell1]> SELECT display_name, vm_state, availability_zone FROM instances WHERE uuid='82d28856-
+------
| display_name | vm_state | availability_zone |
+------
| vm1 | active | nova |
+------
3. Create HA (name is ha1), set AZ (name is az1), add host node01 to HA ha1:
[root@node01 ~]# nova aggregate-show ha1
+----+-
| Id | Name | Availability Zone | Hosts | Metadata | UUID |
+----+-
| 5 | ha1 | az1 | 'node01' | 'availability_
+----+-
4.Query the az of the instance by nova-api:
[root@node01 ~]# nova show 82d28856-
| OS-EXT-
| OS-EXT-
5.In the database use sql to query the current instance of az:
MariaDB [nova_cell1]> SELECT display_name, vm_state, availability_zone FROM instances WHERE uuid='82d28856-
+------
| display_name | vm_state | availability_zone |
+------
| vm1 | active | nova |
+------
Summary:By comparing steps 1, 4 and 2, 5, it is found that the data obtained by vm1 through nova-api is inconsistent with the data in the instances database table, and the availability_
In addition, you can reproduce the problem through horizon.
Changed in nova: | |
assignee: | nobody → sunjiazz (sunjiazz) |
tags: | added: availability-zones |
Changed in nova: | |
status: | New → Triaged |
summary: |
- Fail to filter the list of instances by the available zone + Fail to filter the list of instances by availability zone |
Which release is this against? master (rocky)?