test_fail_set_az fails intermittently with "AssertionError: OpenStackApiException not raised by _set_az_aggregate"
Bug #1844174 reported by
Eric Fried
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Matt Riedemann |
Bug Description
Since 20190910 we've hit this 10x: 8x in functional and 2x in functional-py36
It looks to be a NoValidHosts caused by
2019-09-16 15:10:21,389 INFO [nova.filters] Filter AvailabilityZon
2019-09-16 15:10:21,390 INFO [nova.filters] Filtering removed all hosts for the request with instance ID 'e1ae6109-
Here's one example: https:/
or pasted here for when ^ expires: http://
tags: | added: gate-failure testing |
Changed in nova: | |
assignee: | nobody → Matt Riedemann (mriedem) |
Changed in nova: | |
status: | In Progress → Incomplete |
To post a comment you must log in.
Looks like it started with this change:
https:/ /review. opendev. org/#/c/ 671075/ 21/nova/ tests/functiona l/test_ aggregates. py
I'm not sure what about that is tickling the change, but changing AggregateReques tFiltersTest to inherit from ProviderUsageBa seTestCase might have something to do with it.
My guess is that since ProviderUsageBa seTestCase does a lot of fixture and service setup, like api/conductor/ scheduler, and the existing AggregateReques tFiltersTest class is also doing that stuff, when we set az metadata on aggregates it's only getting sync'ed to one scheduler process and not both and that's why we have intermittent failures.