Encountered after package install failure on consumergroup. All subsequent package install command would hang indefinitely. [root@pulp-qe ~]# pulp-admin package install --consumerid=foo -n patb Created task id: c5dbc1c0-f3f2-11df-8913-5452001e3352 ...................................................................................................... Tailing /var/log/pulp/pulp.log reveals that the task is not being created. Immediately after restarting goferd, all the backed up tasks get flushed and executed. This issue cannot be reproduced deterministically at the moment, but is frequently encountered during nightly automation run.
I'm struggling to reproduce this but I'll keep trying. (In reply to comment #0) > Encountered after package install failure on consumergroup. > > All subsequent package install command would hang indefinitely. > > [root@pulp-qe ~]# pulp-admin package install --consumerid=foo -n patb > Created task id: c5dbc1c0-f3f2-11df-8913-5452001e3352 > ...................................................................................................... > > Tailing /var/log/pulp/pulp.log reveals that the task is not being created. > Immediately after restarting goferd, all the backed up tasks get flushed and > executed. If no task is being created on the server, then no requests are being sent to the agent. So, I wonder how bouncing goferd would help? On another note: Do you see anything in the gofer/agent.log that would indicate that yum is hanging and tying up the agent?
*** This bug has been marked as a duplicate of bug 655851 ***