Bug 975894 - volume cloning is failing with I/O error
Summary: volume cloning is failing with I/O error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-packstack
Version: 4.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: async
: 3.0
Assignee: Martin Magr
QA Contact: Dafna Ron
URL:
Whiteboard:
Depends On: 975052
Blocks: 974575
TreeView+ depends on / blocked
 
Reported: 2013-06-19 14:30 UTC by Eric Harney
Modified: 2016-04-26 23:23 UTC (History)
16 users (show)

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.
Clone Of: 975052
Environment:
Last Closed: 2013-07-15 19:16:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1191812 0 None None None Never
OpenStack gerrit 33553 0 None None None Never
OpenStack gerrit 34176 0 None None None Never
Red Hat Product Errata RHBA-2013:1058 0 normal SHIPPED_LIVE Red Hat OpenStack 3.0 bug fix advisory 2013-07-15 23:16:24 UTC

Comment 1 Martin Magr 2013-06-24 09:36:44 UTC
Backported to grizzly branch https://review.openstack.org/34176 .

Comment 3 Haim 2013-07-14 12:41:39 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

Comment 4 Stephen Gordon 2013-07-15 16:59:19 UTC
Wouldn't users following the manual install path need to enable this as well? Was a documentation bug filed?

Comment 6 errata-xmlrpc 2013-07-15 19:16:43 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.

http://rhn.redhat.com/errata/RHBA-2013-1058.html

Comment 7 Martin Magr 2013-07-16 13:16:26 UTC
Yes, IMHO they will have to enable this as well.


Note You need to log in before you can comment on or make changes to this bug.