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:
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