Hide Forgot
Created attachment 815021 [details] log files from install Description of problem: ======== END OF STDOUT ======== 2013-10-22 09:48:46::DEBUG::sequences::48::root:: Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/packstack/installer/core/sequences.py", line 46, in run self.function(config) File "/usr/lib/python2.6/site-packages/packstack/plugins/puppet_950.py", line 182, in applyPuppetManifest waitforpuppet(currently_running) File "/usr/lib/python2.6/site-packages/packstack/plugins/puppet_950.py", line 167, in waitforpuppet validate_logfile(log) File "/usr/lib/python2.6/site-packages/packstack/modules/puppet.py", line 88, in validate_logfile raise PuppetError(message) PuppetError: Error appeared during Puppet run: 192.168.200.227_prescript.pp Error: Execution of '/usr/bin/yum -d 0 -e 0 -y install openstack-selinux' returned 1: Error: Nothing to do You will find full trace in log /var/tmp/packstack/20131022-094539-GHveFT/manifests/192.168.200.227_prescript.pp.log
This basically means that there's no openstack-selinux package is available in yum repos. But such message should be "morphed" to message which gives some hint. What version of packstack has been used? On which version of Fedora has it been used?
RHEL 6.4 multi-node install Oct 22 08:36:25 Installed: openstack-packstack-2013.2.1-0.11.dev806.el6.noarch Yum logs attached, you can see openstack-selinux is installed. The rpm must be available in the repo. openstack-selinux-0.1.2-11.el6.noarch
According to /logs/rh-net-compute/log/yum.log it is not installed. So I guess 192.168.200.227 is rh-net-compute.
So what I believe is happening here is this... If EPEL is not enabled in the packstack config, then the rdo-release rpm is not installed on any of the nodes. This is causing the openstack rpms not to be found on the additional node.
Ah yes, that's true. Currently RDO repo is only installed together with EPEL repo. This behaviour will be corrected with fix for bug #990642, eg. RDO repo will be installed on remote host automatically if it installed on host where packstack is running. So this should be closed as NOTABUG, but since message has not been changed I will leave it open for the fix https://review.openstack.org/53159