Description of problem: yum-updatesd and pupplet is blocking access to yum instead of informing about updates. Yes, it shows the info, but what when I don't have time to update and want install software? Version-Release number of selected component (if applicable): How reproducible: Run Fedora, when updates daemon is enabled and try to install software, when updates are available. Actual results: Blocked access. Expected results: Not blocked access.
Why is this filed against puppet ? Doesn't look like a puppet problem to me .. please reassign to somebody more appropriate
Reassigning to Jeremy, since he's the owner of yum-updatesd
Created attachment 290909 [details] Strace of yum. I have the same situation. If I try to install software I get the following message: (e.g. from "yum install httpd"). My updates don't happen. I suspect that I may have another repository active Existing lock /var/run/yum.pid: another copy is running as pid 16872. Another app is currently holding the yum lock; waiting for it to exit... Worse; yum-updatesd doesn't respond to kill -1 or kill -15. I have to do a kill -9 and risk (in theory) database corruption. This is with: yum-updatesd-3.2.8-2.fc7 Attached is an strace of yum-updatesd sitting there doing not much.
Created attachment 291475 [details] command history
Comment on attachment 291475 [details] command history I have the same problem, and no update until kill process which hangs...
Not sure if I should say this, but openSUSE has similliar issue with their zypper :> .
Fedora 8's yum-updatesd should be a lot better in this respect