Bug 1052948

Summary:	Could not start Service[libvirt]: Execution of '/etc/init.d/libvirtd start' returned 1
Product:	[Community] RDO	Reporter:	Felipe Alfaro Solana <felipe.alfaro>
Component:	openstack-packstack	Assignee:	Ivan Chavero <ichavero>
Status:	CLOSED CURRENTRELEASE	QA Contact:	yeylon <yeylon>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	aortega, derekh, srevivo, yeylon
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	openstack-packstack-2013.2.1-0.36.dev1013.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-30 23:07:27 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 Felipe Alfaro Solana 2014-01-14 13:39:47 UTC

Description of problem:
When running on RHEL 6.4 (Santiago), packstack --allinone might fail because puppet scripts invoke "/etc/init.d/libvirtd start" instead of "service libvirtd start". Apparently, libvirtd is very sensitive to environment variables.

Version-Release number of selected component (if applicable):
RHEL 6.4 (Santiago)

How reproducible:
Always

Steps to Reproduce:
1. packstack --allinone
2. fails with the following error: SequenceError: Error during puppet run : Error: Could not start Service[libvirt]: Execution of '/etc/init.d/libvirtd start' returned 1

Problem is that libvirtd fails to start with a non-empty environment:

# libvirtd
libvirtd: initialization failed

No messages are logged anywhere.

However,

# env -i TERM=$TERM PATH=$PATH libvirtd

works as expected.

Actually, the "service" shell script wrapper invokes the service by running it with an empty environment (just like shown above).

Actual results:
packstack --allinone fails

Expected results:
packstack --allinone should complete. Starting libvirtd by hand by using "service libvirtd start", then re-running packstack with the generated answer file works as a workaround.

Additional info:

Comment 1 Ivan Chavero 2014-04-14 22:50:01 UTC

This problem does not appear in the curren packstack version.
openstack-packstack-2013.2.1-0.36.dev1013.el6
openstack-packstack-2013.2.1-0.36.dev1013.fc20