Bug 1254755
| Summary: | Cinder LVM iSCSI driver with LIO helper fails to handle multiple concurrent requests to attach/detach volumes | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Jon Schlueter <jschluet> |
| Component: | openstack-cinder | Assignee: | Gorka Eguileor <geguileo> |
| Status: | CLOSED ERRATA | QA Contact: | Yogev Rabl <yrabl> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.0 (RHEL 7) | CC: | ddomingo, dmaley, dshetty, ebarrera, eharney, geguileo, jbuchta, jschluet, jwaterwo, lyarwood, nlevinki, pcaruana, scohen, sgotliv, yeylon |
| Target Milestone: | z5 | Keywords: | Triaged, ZStream |
| Target Release: | 5.0 (RHEL 6) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-cinder-2014.1.4-3.el6ost | Doc Type: | Bug Fix |
| Doc Text: |
Previous releases did not have synchronized access to configfs in rtslib. This made it possible for rtstool or rtslib to attempt access to an element that had just been removed mid-loop by another Block Storage request (and was, therefore, non-existent). This, in turn, could result in any of the following exceptions:
- .dump()
- KeyError
- IOError
- RTSLibError on storage_object
This release implements synchronized access to all rtstool calls that access or modify configfs. With this, concurrent access from multiple threads and processes now work consistently.
|
Story Points: | --- |
| Clone Of: | 1221614 | Environment: | |
| Last Closed: | 2015-09-10 11:47:41 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: | 1221614, 1289526 | ||
| Bug Blocks: | 1227404, 1227405 | ||
|
Comment 1
Jon Schlueter
2015-08-18 18:58:33 UTC
verified on openstack-cinder-2014.1.5-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. https://rhn.redhat.com/errata/RHBA-2015-1759.html |