Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1242936

Summary:	Loop device is not associated with LVM2 PV file created on controller after reboot
Product:	Red Hat OpenStack	Reporter:	Marian Krcmarik <mkrcmari>
Component:	rhosp-director	Assignee:	chris alfonso <calfonso>
Status:	CLOSED DUPLICATE	QA Contact:	yeylon <yeylon>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	7.0 (Kilo)	CC:	hbrock, jslagle, mburns, rhel-osp-director-maint, srevivo
Target Milestone:	---
Target Release:	Director
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-07-14 17:59:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Marian Krcmarik 2015-07-14 12:45:25 UTC

Description of problem:
There is no associated loop device with LVM2 PV file which acts as cinder-volumes Volume group on basic deployment deployed by OSP-d on controller node which holds cinder service.
I believe this happens after the controller node is restarted. I have to manually associate loopback device with the LVM2 PV file which is used as cinder volumes storage by running:

$ sudo vgscan
  Reading all physical volumes.  This may take a while...
# losetup /dev/loop0 /var/lib/cinder/cinder-volumes
# vgdisplay 
  --- Volume group ---
  VG Name               cinder-volumes
  System ID             
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  65
  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               4.88 GiB
  PE Size               4.00 MiB
  Total PE              1249
  Alloc PE / Size       0 / 0   
  Free  PE / Size       1249 / 4.88 GiB
  VG UUID               e8RNec-uUbc-3Ass-75gW-eUn9-0R71-GzDnYt

The volume log shows an error:
2015-07-14 08:08:46.952 9529 WARNING cinder.volume.manager [req-4689cd2f-aab2-468b-a132-80e3cdb74bd3 - - - - -] Unable to update stats, LVMVolumeDriver -3.0.0 (config name tripleo_iscsi) driver is uninitialized.


Version-Release number of selected component (if applicable):
2015-07-02.1

How reproducible:
Always

Steps to Reproduce:
1. Deploy OS with OSP-d in basic scenario with one controller and one compute node where controller holds the cinder service with volumes stored in VG represented by LVM2 PV file.
2. probably restart controller node

Actual results:
The file is not associated with loopback device so system cannot see any VG and thus cinder service does not work as expected

Expected results:
I guess installer is supposed to set it correctly - to associate the file with loopback device after restart.

Additional info:

Comment 3 James Slagle 2015-07-14 17:59:36 UTC


*** This bug has been marked as a duplicate of bug 1241644 ***