Description of problem: Package install on remote clients seem to be not happening. The task just goes on with [root@preethi ~]# pulp-admin package install -n zsh --consumerid=10.16.79.198 Created task id: 158727a8-f646-11df-b78c-002564a85a58 ... 1. I have a local & remote client 2. Remote client is registered and bound to the the repo with pulp-client consumer 3. on the server if I do a consumer list its is show as [root@preethi ~]# pulp-admin consumer list +------------------------------------------+ Consumer Information +------------------------------------------+ Id 10.16.79.198 Description None Subscribed Repos /pulp/api/consumers/10.16.79.198/repoids/ Additional info {} Id preethi.userys.redhat.com Description None Subscribed Repos /pulp/api/consumers/preethi.userys.redhat.com/repoids/ Additional info {} Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
[root@preethi ~]# rpm -qa |grep pulp pulp-common-0.0.108-1.fc13.noarch pulp-client-0.0.108-1.fc13.noarch pulp-0.0.108-1.fc13.noarch [root@preethi ~]# rpm -qa |grep gofer gofer-0.1-1.fc13.noarch gofer-lib-0.1-1.fc13.noarch
The reason this was happening on pulp-qe and pulp-qe-client is because your client messaging was pointing to localhost.. change /etc/gofer/agent.conf to point to your server instead of localhost and restart gofer.
After making the modification to /etc/gofer/agent.conf, the package install on remote client is successful. However the client does not report this, instead it continues to hang indefinitely. Tailing the log reveals that the pkg install request is sent to gofer but a reply was never sent back to the client. Restarting gofer does not alleviate this issue. Package install was verified w/ rpm -qi
(In reply to comment #3) > After making the modification to /etc/gofer/agent.conf, the package install on > remote client is successful. However the client does not report this, instead > it continues to hang indefinitely. Hang how? Does it continue to print the (..)?
Yes,I think what David means it continues to print .... indefinitely (he is in class this week.)
I can't reproduce, closing. It may have been environmental, timing, fixed inadvertently with changes to gofer and/or tasking subsystem in pulp. Or, it still may exist. We'll keep an eye out for it.
*** Bug 655102 has been marked as a duplicate of this bug. ***