Bug 1042915 - ThinLVM space calculation fails if thin pool LV is not activated
Summary: ThinLVM space calculation fails if thin pool LV is not activated
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: z1
: 4.0
Assignee: Eric Harney
QA Contact: Giulio Fidente
URL:
Whiteboard:
Depends On:
Blocks: 975606
TreeView+ depends on / blocked
 
Reported: 2013-12-13 15:50 UTC by Eric Harney
Modified: 2016-04-26 13:33 UTC (History)
5 users (show)

Fixed In Version: openstack-cinder-2013.2.1-3.el6ost
Doc Type: Bug Fix
Doc Text:
Prior to this update, ThinLVM driver space calculation failed if the thin pool LV was not active. As a result, the volume driver remained uninitialized and various operations could not be performed. This update enables the thin pool LV at driver initialization time. Consequently, the Block Storage ThinLVM driver can start up and function correctly, despite the thin pool being inactive prior to the volume service starting.
Clone Of:
Environment:
Last Closed: 2014-01-23 14:23:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1260773 0 None None None Never
OpenStack gerrit 62018 0 None None None Never
OpenStack gerrit 64848 0 None None None Never
Red Hat Product Errata RHBA-2014:0046 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform 4 Bug Fix and Enhancement Advisory 2014-01-23 00:51:59 UTC

Description Eric Harney 2013-12-13 15:50:24 UTC 
Description of problem:
ThinLVM space calculation fails if thin pool LV is not activated


Steps to Reproduce:
1.  lvchange -a n cinder-volumes/cinder-volumes-pool
2.  service openstack-cinder-volume restart
3.  cinder create 1
Comment 2 Giulio Fidente 2014-01-14 12:30:59 UTC 
verified using openstack-cinder-2013.2.1-4.el6ost.noarch
Comment 5 Lon Hohberger 2014-02-04 17:20:28 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://rhn.redhat.com/errata/RHBA-2014-0046.html
Note You need to log in before you can comment on or make changes to this bug.