Service does not start if volumes exist
Bug #1043760 reported by
Unmesh Gurjar
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cinder |
Fix Released
|
Critical
|
Unassigned | ||
Bug Description
Tested on Branch: master (commitID: 4533e5b45096437
Configuration:
Use the default volume driver ISCSIDriver.
Scenario:
1. Create a volume (of any size say 1G).
2. After the volume creation succeeds, stop the Cinder volume service.
3. Now, start the volume service back again.
Observations:
On reverting the changes in commit ID 5b34c99c734a574
Regression issues:
The call to 'ensure_export( )' on existing volumes will fail at all places. Example: "os-image-create" extension (for creating volume from an image) fails in 'ensure_export'.
Stack Trace: http://
Revision history for this message
| John Griffith (john-griffith) wrote | #1 |
| Changed in cinder: | |
| status: | New → Triaged |
| status: | Triaged → In Progress |
| importance: | Undecided → Critical |
| milestone: | none → folsom-rc1 |
| Changed in cinder: | |
| status: | In Progress → Fix Committed |
| Changed in cinder: | |
| status: | Fix Committed → Fix Released |
| Changed in cinder: | |
| milestone: | folsom-rc1 → 2012.2 |
To post a comment you must log in.
This should be addressed by changes in: https:/