ERROR : Error during puppet run : err: /Stage[main]/Nova::Compute/Nova::Generic_service[compute]/Package[nova-compute]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install openstack-nova-compute' returned 1: Existing lock /var/run/yum.pid: another copy is running as pid 24337. IMHO, yum is executed periodically to check for updates, at least on RHEL... Thus, that shouldn't kill packstack.
Can you please upload setup.log, so I can check if this puppet error can be ignored? Thanks in advance.
How to reproduce: When packstack is running and preparing, issue yum install (something currently not installed), yum will ask: will install ... is this ok (y/n)?" <- don't do anything here. You'll get a lock and packstack can't execute yum at all.
And: packstack should wait, until the lock is released.
Packstack can never make 100% sure yum is unlocked (it might get locked between Packstack checking and Puppet executing yum). Actually wondering, whether this should rather be fixed in Puppet upstream.
Well, that's what I wanted to checkout from the log: if puppet is waiting for yum unlock and packstack is catching it as an error or puppet just fails when yum is locked. Will try to reproduce that and see what I can do.
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle. Changing version to '20'. More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.