status=None while delete is in progress
Bug #1503390 reported by
Mark Sturdevant
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
High
|
NidhiMittalHada |
Bug Description
When deleting snapshots and getting snapshot lists, testing has shown that the status of a snapshot may be None. It looks like this happens when the snapshot instance is has been deleted, but the snapshot itself has not yet been deleted. This would happen in a very small window.
A snapshot with no instances should not be included in the list -- or perhaps it could be in the list, but should have a status of "deleting".
It seems the status handling and/or the order of deletion of the snapshot and its final (only) instance need to be fixed.
The same problem has been caught with deleted shares returning a status of None.
Changed in manila: | |
importance: | Undecided → High |
status: | New → Triaged |
milestone: | none → mitaka-1 |
Changed in manila: | |
assignee: | nobody → NidhiMittalHada (nidhimittal19) |
Changed in manila: | |
milestone: | mitaka-1 → mitaka-2 |
Changed in manila: | |
milestone: | mitaka-2 → mitaka-3 |
To post a comment you must log in.
This has been seen with shares as well as snapshots. Our "instance" logic needs to be improved.