Bug 1111694
| Summary: | cannot attach volume after volume snapshot create/delete | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Scott Lewis <sclewis> |
| Component: | openstack-cinder | Assignee: | Eric Harney <eharney> |
| Status: | CLOSED ERRATA | QA Contact: | Dafna Ron <dron> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 5.0 (RHEL 7) | CC: | afazekas, dnavale, eharney, fpercoco, mburns, nlevinki, scohen, sgotliv, yeylon, yrabl |
| Target Milestone: | rc | ||
| Target Release: | 5.0 (RHEL 6) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
In previous releases, it was possible to delete a volume's snapshot to prevent the volume from being attached to an instance. This was because the commands used for deleting a volume did not contain any commands to deactivate (before snapshot deletion) and reactivate (after snapshot deletion) volumes. As such, when deleting a volume's snapshot, it was possible for the volume to be left with incorrect flags that would render it unattachable to an instance.
With this release, volume snapshot deletion now works with the right commands, ensuring that volumes are deactivated and reactivated as expected.
|
Story Points: | --- |
| Clone Of: | 1096489 | Environment: | |
| Last Closed: | 2014-07-28 18:57:49 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1091716, 1096489 | ||
| Bug Blocks: | |||
|
Comment 2
Yogev Rabl
2014-07-13 07:03:12 UTC
How did it fail? When the snapshot was deleted I've noticed that the volume from which it was created, vanished as well. It seems that the deletion is going through the whole chain. Need log files / more information about test failure. Eric, the fix wasn't in the version that I've tested it on. Now, the bug is verified in version: openstack-cinder-2014.1.1-1.el6ost.noarch python-cinderclient-1.0.9-1.el6ost.noarch python-cinder-2014.1.1-1.el6ost.noarch Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-0955.html |