Back to bug 1042915

Who When What Removed Added
Eric Harney 2013-12-13 15:50:38 UTC CC gfidente
Assignee rhos-maint eharney
Eric Harney 2013-12-13 15:50:53 UTC Link ID OpenStack gerrit 62018
Eric Harney 2013-12-13 15:51:41 UTC CC jobernar
Blocks 975606
Eric Harney 2013-12-13 15:51:56 UTC Status NEW ON_DEV
Scott Lewis 2013-12-13 18:16:23 UTC Keywords ZStream
RHEL Program Management 2013-12-18 01:27:52 UTC Target Release --- 4.0
Eric Harney 2014-01-03 21:55:49 UTC Link ID OpenStack gerrit 64848
Andrej Golis 2014-01-06 11:48:40 UTC QA Contact hateya dron
Eric Harney 2014-01-07 20:16:20 UTC Status ON_DEV POST
Eric Harney 2014-01-07 21:36:15 UTC Doc Text Cause: ThinLVM driver space calculation fails if thin pool LV is not active

Consequence: Volume driver is uninitialized and many operations cannot be performed

Fix: Enable the thin pool LV at driver initialization time

Result: Cinder's ThinLVM driver can start up and function correctly when the thin pool was not active prior to the volume service starting
Eric Harney 2014-01-07 21:37:35 UTC Whiteboard mid-Jan
Eric Harney 2014-01-08 16:41:46 UTC Fixed In Version openstack-cinder-2013.2.1-3.el6ost
Eric Harney 2014-01-08 16:59:18 UTC Status POST MODIFIED
Scott Lewis 2014-01-08 19:44:00 UTC Target Milestone async A1
Scott Lewis 2014-01-08 19:53:20 UTC Whiteboard mid-Jan
errata-xmlrpc 2014-01-10 20:49:31 UTC Status MODIFIED ON_QA
John Skeoch 2014-01-13 01:18:44 UTC CC hateya
Dafna Ron 2014-01-13 11:02:32 UTC QA Contact dron gfidente
Giulio Fidente 2014-01-14 12:30:59 UTC Status ON_QA VERIFIED
Martin Lopes 2014-01-20 06:23:35 UTC CC mlopes
Doc Text Cause: ThinLVM driver space calculation fails if thin pool LV is not active

Consequence: Volume driver is uninitialized and many operations cannot be performed

Fix: Enable the thin pool LV at driver initialization time

Result: Cinder's ThinLVM driver can start up and function correctly when the thin pool was not active prior to the volume service starting
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.
errata-xmlrpc 2014-01-22 16:09:15 UTC Status VERIFIED RELEASE_PENDING
Scott Lewis 2014-01-23 14:23:55 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2014-01-23 09:23:55 UTC
Perry Myers 2016-04-26 13:33:19 UTC CC pmyers

Back to bug 1042915