nova-scheduler is not consistent in host_aggregates_map and database
Bug #1699054 reported by
D G Lee
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
Test steps:
1. There are multiple nova-scheduler services.
2. The value of default_
3. Create an aggregate and its availability_zone is 'az-test'.
4. Add all hosts to the new aggregate.
In step 4, the nova api will send asynchronous RPC message to all nova schedulers to update aggregate information in memory. Because of rabbitmq fails，some nova scheduler can't consume the message from nova api, so the data is not consistent in memory and database. create the instance with 'az-test' availability zone will fail because without 'az-test' availability_zone in nova scheduler.
There is no way to know that host_aggregates_map is inconsistent with the database.
| tags: | added: scheduler |
| Changed in nova: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Related fix proposed to nova (master) | #1 |
To post a comment you must log in.
Related fix proposed to branch: master
Review: https:/