Bug 1547578
| Summary: | Nova assumes that a volume is fully detached from the compute if the volume is not defined in the instance's libvirt definition | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Sahid Ferdjaoui <sferdjao> | |
| Component: | openstack-nova | Assignee: | Sahid Ferdjaoui <sferdjao> | |
| Status: | CLOSED ERRATA | QA Contact: | Joe H. Rahme <jhakimra> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 12.0 (Pike) | CC: | berrange, dasmith, eglynn, jamsmith, jhakimra, kchamart, marjones, mbooth, mwitt, sbauza, sferdjao, sgordon, slinaber, srevivo, vromanso | |
| Target Milestone: | z3 | Keywords: | TestOnly, Triaged, ZStream | |
| Target Release: | 12.0 (Pike) | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | openstack-nova-16.0.4-6.el7ost | Doc Type: | Bug Fix | |
| Doc Text: |
Prior to this update, a volume detach operation performed under certain failure scenarios could result in the removal of a volume's libvirt definition without full removal of the associated logical volume (LUN) from the host. This allowed Cinder to incorrectly perform subsequent operations while the compute host still had active paths to the device.
As of this update, even under a failure scenario, Nova compute attempts to disconnect the LUN from the host. The result is a better release of the logical volume on the host.
|
Story Points: | --- | |
| Clone Of: | 1547576 | |||
| : | 1547580 (view as bug list) | Environment: | ||
| Last Closed: | 2018-08-20 12:55:29 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: | 1505595, 1547576 | |||
| Bug Blocks: | 1547580 | |||
|
Comment 1
Lon Hohberger
2018-05-22 10:37:57 UTC
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. https://access.redhat.com/errata/RHSA-2018:2332 |