Red Hat Bugzilla – Bug 1240195
The logical volume for cinder storage is too small
Last modified: 2017-03-14 20:46:49 EDT
Description of problem: I deployed on bare metals. Each controller is a pretty strong machine with 500GB disk space, 12 CPUs and 24GB RAM. Cinder complains that it can't allocate any space, and this also causes many tempest tests to fail. This is the output from pvdisplay and vgdisplay: [root@overcloud-controller-0 ~]# pvdisplay --- Physical volume --- PV Name /dev/loop2 VG Name cinder-volumes PV Size 4.88 GiB / not usable 3.00 MiB Allocatable yes PE Size 4.00 MiB Total PE 1249 Free PE 225 Allocated PE 1024 PV UUID Lpg1wQ-xeGV-agZx-knEh-iCf3-vcCp-89BXSC [root@overcloud-controller-0 ~]# vgdisplay --- Volume group --- VG Name cinder-volumes System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 140 VG Access read/write VG Status resizable MAX LV 0 Cur LV 4 Open LV 0 Max PV 0 Cur PV 1 Act PV 1 VG Size 4.88 GiB PE Size 4.00 MiB Total PE 1249 Alloc PE / Size 1024 / 4.00 GiB Free PE / Size 225 / 900.00 MiB VG UUID oIfltY-kmcV-OX1W-gUQx-BZHQ-fGIE-3sk7HG How reproducible: 100% Steps to Reproduce: 1. Deploy on bare metals 2. Log in to the controller nodes and run pvdisplay and vgdisplay Actual results: The volume group size is 4GB Expected results: The disk should be large, in proportion with the available hardware.
as a workaround, the loopback device size can be customized adding into static hieradata something like: cinder::setup_test_volume::size: 8G
I tried to increase the cinder volume on all controller nodes. After logging in to each of them and running "sudo -i" I did this: # create a 40GB file in /var/lib/cinder/ cd /var/lib/cinder/ dd if=/dev/zero of=cinder-volumes2 bs=102400 count=409600 # add the file to losetup losetup /dev/loop3 /var/lib/cinder/cinder-volumes2 losetup -l # just to test that it worked # create a physical volume pvcreate /dev/loop3 # extend the logical volume "cinder-volumes" to the new physical volume vgextend cinder-volumes /dev/loop3 # test that it worked pvdisplay vgdisplay # restart cinder systemctl restart openstack-cinder-api.service openstack-cinder-scheduler.service openstack-cinder-volume.service ... It didn't quite help me but maybe it will help someone else (I had other problems in my deployment).
[root@overcloud-controller-1 ~]# pvdisplay --- Physical volume --- PV Name /dev/loop2 VG Name cinder-volumes PV Size 10.04 GiB / not usable 4.00 MiB Allocatable yes PE Size 4.00 MiB Total PE 2569 Free PE 2569 Allocated PE 0 PV UUID AUrYFi-a3Yf-diqT-WXbb-x4be-L5ph-HRzbD3 [root@overcloud-controller-1 ~]# vgdisplay --- Volume group --- VG Name cinder-volumes System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 1 VG Access read/write VG Status resizable MAX LV 0 Cur LV 0 Open LV 0 Max PV 0 Cur PV 1 Act PV 1 VG Size 10.04 GiB PE Size 4.00 MiB Total PE 2569 Alloc PE / Size 0 / 0 Free PE / Size 2569 / 10.04 GiB VG UUID XfBbtz-tyYF-ihlv-0Y5G-PBPx-3gbI-yZyCld Verified on: openstack-tripleo-heat-templates-0.8.9-1.el7ost.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. https://rhn.redhat.com/errata/RHEA-2016-0604.html