Generic catchall bug for non triaged bugs where a server doesn't reach it's required state
Bug #1260537 reported by
Sean Dague
This bug affects 25 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tempest |
Invalid
|
High
|
Unassigned | ||
Bug Description
This is the generic catch all for a whole lot of bugs that register as Tempest bugs which are about a compute resource not reaching the state it was supposed to. In most cases these are really Nova race conditions. If there is no real debug in the bugs they'll just be added to this one.
Part of this is collecting how often this gets registered and if there is a new kind of test we can add that would move this from a 5% fail to a 100% fail so we could fix it easier.
| Changed in tempest: | |
| status: | New → Confirmed |
| importance: | Undecided → High |
Revision history for this message
| Matt Riedemann (mriedem) wrote | #1 |
| Changed in tempest: | |
| status: | Confirmed → Invalid |
To post a comment you must log in.
I think we can invalidate this now. At the time we had a lot of timeouts going on and I think that kind of failure has mostly settled down, or we have more specific bugs for tracking these things - and if we don't, we're not doing a very good job of adding good diagnostic logging to nova to fingerprint the failures.