Nova Affinity filters no longer work
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
Undecided
|
Matt Riedemann |
Bug Description
A recent change to devstack [1] has broken RPC between Nova compute and Nova scheduler in devstack and this in turn is affecting the affinity and anti-affinity filters.
The Trove project has a negative gate test which tests anti-affinity as part of a DB cluster replica deploy and this test is failing because Nova is allowing 2 instances on the same host.
The lack of RPC from compute to the scheduler can be seen in the Nova gate logs from before and after the change. The message "Successfully synced instances from host' appears in the scheduler log before the change [2].
Based on the commit message in this change and related changes, it may have been intentional to break the RPC comm between compute and scheduler to test for cells. If that is the case then we need another way to allow the affinity filters to work in this set up. I have tried setting 'track_
After the change the transport_url settings in Nova conf differ between the scheduler and the compute and even have different values in the compute conf itself:
nova scheduler:
[DEFAULT]
transport_url = rabbit:
[oslo_messaging
transport_url = rabbit:
nova compute:
[DEFAULT]
transport_url = rabbit:
[oslo_messaging
transport_url = rabbit:
[1] https:/
[2] http://
[3] https:/
[4] http://
[5] https:/
no longer affects: | devstack |
Yeah, this was intentional and will be like this for a bit. Here's your workaround:
https:/ /review. openstack. org/#/c/ 487478/