Bug 993899 - packstack quits, when yum also runs
packstack quits, when yum also runs
Product: Fedora
Classification: Fedora
Component: openstack-packstack (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Martin Magr
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-08-06 08:59 EDT by Matthias Runge
Modified: 2015-06-29 08:14 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-06-29 08:14:58 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Matthias Runge 2013-08-06 08:59:01 EDT
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.
Comment 1 Martin Magr 2013-08-06 10:53:38 EDT
Can you please upload setup.log, so I can check if this puppet error can be ignored? Thanks in advance.
Comment 2 Matthias Runge 2013-08-07 02:08:12 EDT
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.
Comment 3 Matthias Runge 2013-08-07 02:08:51 EDT
And: packstack should wait, until the lock is released.
Comment 4 Sandro Mathys 2013-08-07 02:13:12 EDT
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.
Comment 5 Martin Magr 2013-08-07 03:33:18 EDT
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.
Comment 6 Fedora End Of Life 2013-09-16 12:15:40 EDT
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:
Comment 7 Fedora Admin XMLRPC Client 2013-10-14 05:50:36 EDT
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 8 Fedora Admin XMLRPC Client 2013-10-14 05:51:05 EDT
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 9 Fedora End Of Life 2015-05-29 05:17:36 EDT
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.
Comment 10 Fedora End Of Life 2015-06-29 08:14:58 EDT
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

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.