Bug 1374292

Summary:	Installing undercloud on a VMware VM causes VM to boot into emergency mode
Product:	Red Hat OpenStack	Reporter:	Tzach Shefi <tshefi>
Component:	rhosp-director	Assignee:	Angus Thomas <athomas>
Status:	CLOSED DUPLICATE	QA Contact:	Omri Hochman <ohochman>
Severity:	low	Docs Contact:
Priority:	low
Version:	9.0 (Mitaka)	CC:	dbecker, mburns, morazi, rhel-osp-director-maint
Target Milestone:	---
Target Release:	10.0 (Newton)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-08 12:38:57 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 Tzach Shefi 2016-09-08 12:08:04 UTC

Description of problem: This probably isn't officially supported and sure isn't the typical use case but it might be needed/good for POC with people who utilize VMware.  

Once I #openstack undercloud install (which BTW installs fine and works) any subsequent reboot of OSPd VM hits emergency mode.

Reason being Home_LV isn't set to active state.
My workaround once in emergency mode: 
#lvchange -ay /dev/vg0/lv_home
#exit 


Happens every time on both OSPd 8 or 9, I've hit this like 20+ times. Up to and before undercloud install VM reboots without problems.

Version-Release number of selected component (if applicable):
RHEL 7.2 
OSPd 8 as well as 9.
VMware 5.5u3

How reproducible: 
Every time 100%, every install of OSPd on a VMware VM causes this! 

Steps to Reproduce:
1. Bring up a VMware VM
2. Install OSPd, up to this step #openstack undercloud install, VM is OK and reboots without issues.
3. Once undercloud is installed, undercloud works fine, but if you have to reboot the VM it will hit this bug. 
4. Issue the #lvs command check Attr for state of home_lv  it should also include ao  like the other lvs. 

Actual results:
OSPd VM boots into emergency mode, home_lv isn't set to active. 

Expected results:
OSPd VM should boot without hitting emergency mode. 

Additional info:
For access to a VMware system email/ping me. 

I doubt this would be fixed anytime soon if at all, none the less figured I should report it any way.

Comment 2 Mike Burns 2016-09-08 12:38:57 UTC

This is a long standing issue described in bug 1323024 (and other duplicates).  The documentation explicitly mentions one of the solutions:

https://access.redhat.com/documentation/en/red-hat-openstack-platform/9/paged/director-installation-and-usage/chapter-2-requirements

Section 2.2

IMPORTANT
Ensure the Undercloud’s file system only contains a root and swap partitions if using Logical Volume Management (LVM). For more information, see the Red Hat Customer Portal article "Director node fails to boot after undercloud installation".

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