Bug 975894
| Summary: | volume cloning is failing with I/O error | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Eric Harney <eharney> |
| Component: | openstack-packstack | Assignee: | Martin Magr <mmagr> |
| Status: | CLOSED ERRATA | QA Contact: | Dafna Ron <dron> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 4.0 | CC: | abaron, agk, ajeain, aortega, apevec, dallan, derekh, eharney, gfidente, hateya, jkt, kdas, mmagr, pbrady, sclewis, sgordon |
| Target Milestone: | async | Keywords: | ZStream |
| Target Release: | 3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-packstack-2013.1.1-0.23.dev642.el6ost | Doc Type: | Bug Fix |
| Doc Text: |
LVM autoextend is disabled by default on Red Hat Enterprise Linux 6.4. As a result I/O errors were encountered attempting to clean up the snapshot that created when cloning a volume. To workaround this issue PackStack has been updated and now enables LVM autoextend automatically.
|
Story Points: | --- |
| Clone Of: | 975052 | Environment: | |
| Last Closed: | 2013-07-15 19:16:43 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: | 975052 | ||
| Bug Blocks: | 974575 | ||
|
Comment 1
Martin Magr
2013-06-24 09:36:44 UTC
moving to verified, however, found a similar bug when creating cloned volumes in a loop. creation of one volume succeeded. see https://bugzilla.redhat.com/show_bug.cgi?id=984280 Wouldn't users following the manual install path need to enable this as well? Was a documentation bug filed? 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/RHBA-2013-1058.html Yes, IMHO they will have to enable this as well. |