Bug 1096489
| Summary: | cannot attach volume after volume snapshot create/delete | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | yeylon <yeylon> | |
| 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, ddomingo, eharney, fpercoco, mburns, sclewis, scohen, srevivo, yeylon, yrabl | |
| Target Milestone: | rc | Keywords: | TestBlocker | |
| Target Release: | 5.0 (RHEL 7) | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | openstack-cinder-2014.1-4.el7ost | Doc Type: | Bug Fix | |
| Doc Text: |
In previous releases, it was possible for the deletion of a volume's snapshot to prevent the volume from being attached to an instance. This was because the commands used for volume deletion 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: | 1091716 | |||
| : | 1111694 (view as bug list) | Environment: | ||
| Last Closed: | 2014-07-08 15:31:18 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 | |||
| Bug Blocks: | 1111694 | |||
|
Comment 1
Attila Fazekas
2014-05-15 11:59:50 UTC
validate in version: openstack-nova-cert-2014.1-3.el7ost.noarch openstack-nova-novncproxy-2014.1-3.el7ost.noarch openstack-cinder-2014.1-4.el7ost.noarch python-nova-2014.1-3.el7ost.noarch openstack-nova-console-2014.1-3.el7ost.noarch python-cinder-2014.1-4.el7ost.noarch python-cinderclient-1.0.8-1.el7ost.noarch python-novaclient-2.17.0-2.el7ost.noarch openstack-nova-api-2014.1-3.el7ost.noarch openstack-nova-compute-2014.1-3.el7ost.noarch openstack-nova-conductor-2014.1-3.el7ost.noarch openstack-nova-scheduler-2014.1-3.el7ost.noarch openstack-nova-common-2014.1-3.el7ost.noarch openstack-nova-network-2014.1-3.el7ost.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-0852.html |