Ensure ThinLVM LV is active when cloning or creating from snapshot
Bug #1252423 reported by
Eric Harney
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Medium
|
Eric Harney | ||
Havana |
Fix Released
|
Medium
|
Eric Harney |
Bug Description
Thin-provisioned LVs may not be activated automatically in all cases. (RHEL 6.5 does not activate them automatically by default.)
This causes the volume clone from snapshot dd operation to fail, as the source device does not exist in /dev/mapper/. We should ensure the LV is active before attempting to clone to a new volume.
Changed in cinder: | |
assignee: | nobody → Eric Harney (eharney) |
tags: | added: havana-backport-potential |
tags: | added: grizzly-backport-potential |
Changed in cinder: | |
milestone: | none → icehouse-1 |
status: | Fix Committed → Fix Released |
tags: | removed: havana-backport-potential |
Changed in cinder: | |
importance: | Undecided → Medium |
summary: |
- Ensure ThinLVM LV is active when cloning + Ensure ThinLVM LV is active when cloning from snapshot |
summary: |
- Ensure ThinLVM LV is active when cloning from snapshot + Ensure ThinLVM LV is active when cloning or snapshotting |
summary: |
- Ensure ThinLVM LV is active when cloning or snapshotting + Ensure ThinLVM LV is active when cloning or creating from snapshot |
tags: | removed: grizzly-backport-potential |
Changed in cinder: | |
milestone: | icehouse-1 → 2014.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/57015
Review: https:/