After restarting an instance volume is lost
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Vish Ishaya | ||
Folsom |
Fix Released
|
Medium
|
Vish Ishaya | ||
nova (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Quantal |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
1. Launch instance
2. Attach Volume to instance
3. SSH into instance
4. Verify volume is in device list (it should be /dev/vdb - you can run `lsblk` from inside the instance)
5. Shutdown instance (nova stop uuid)
6. Start instance (nova start uuid)
5. SSH into instance
6. Verify volume is in device list (it should be /dev/vdb - you can run `lsblk` from inside the instance)
Expected: When i ssh into instance after the reboot and check volume devices, the previous volume (/dev/vdb) should exist.
Actual: When i ssh into instance after the reboot and check volume devices, the only one listed is /dev/vda - missing the attached volume.
Also another behavior is that when I try to detach the volume via the dashboard it goes into 'detaching' state for 5 seconds then returns to 'in use' and stays that way.
Related branches
- Openstack Ubuntu Testers: Pending requested
-
Diff: 121 lines (+100/-4)1 file modifieddebian/changelog (+100/-4)
CVE References
Changed in nova: | |
importance: | Undecided → Medium |
status: | New → In Progress |
assignee: | nobody → Vish Ishaya (vishvananda) |
tags: | added: folsom-backport-potential |
Changed in nova: | |
milestone: | none → grizzly-1 |
status: | Fix Committed → Fix Released |
tags: | removed: folsom-backport-potential |
Changed in nova (Ubuntu): | |
status: | New → Fix Released |
Changed in nova (Ubuntu Quantal): | |
status: | New → Confirmed |
Changed in nova: | |
milestone: | grizzly-1 → 2013.1 |
Fix proposed to branch: master /review. openstack. org/14795
Review: https:/