Description of problem: If the thin pool is created with the correct size (roughly the size of the containing volume group), then cinder reports total and available capacity for the volume group and not the thin pool. This causes the scheduler to think there is no capacity (because the thin pool is consuming all of the volume group). For thin LVM, the capacity of the pool should be used in reporting capacity to the scheduler, and not the volume group. Version-Release number of selected component (if applicable): 4.0 How reproducible: Steps to Reproduce: 1. Set lvm_type to 'thin' in cinder.conf 2. Apply thin-pool-creation patch from gerrit: https://review.openstack.org/#/c/54833/ 3. Create a volume Actual results: Newly created volume will immediately enter the 'error' state. Scheduler logs indicate insufficient capacity to satisfy request. Expected results: Volume is created successfully. Additional info: I have submitted a patch for this under review at https://review.openstack.org/#/c/56091/
isn't this a dup of bug 1022714 ?
They are technically two different bugs, although closely related. bug 1022714 is a failure to create the thin pool of the correct size. This bug then follows, once the pool is of sufficient size the capacity reporting is inaccurate which causes a failure to create a volume backed by the pool. The interesting part is that this bug is not easily visible until 1022714 is fixed - only then does it become an obvious error.
*** Bug 1037560 has been marked as a duplicate of this bug. ***
openstack-cinder-2013.2-8.el6ost does *not* include the patch
kudos to Eric, it was my fault, verified using: openstack-cinder-2013.2-8.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. http://rhn.redhat.com/errata/RHEA-2013-1859.html