The client plugin uses the host from /etc/pulp/client.conf, which lets Pulp users make all client configuration changes from that file. Gofer still ships with the builtin plugin enabled, which will use /etc/gofer/agent.conf for the message broker host. That is left at localhost, so gofer will continue to try to connect to a message broker on localhost while it is running. We need to somehow disable the builtin plugin; either by default in gofer or as part of the pulp client installation.
Fixed in gofer 0.23. By default, no URL is defined for the builtin plugin (or the agent.conf) which indicates that no session (connection) to the broker should be established on behalf of the builtin plugin.
I'm not opposed to shipping gofer with the builtin plugin disabled as well. But, chose this approach instead because: Pros: * Leaving it enabled reduces the number of things new gofer users need to do in order to try it out. * Leaves the AgentAdmin functionality available through other plugins like: - hello() : reports agent configuration. - help() : shows info on installed plugins. Cons: * Leaves the TestAction running on pulp installs. Although, this is a reference implementation and really could be removed all together. In 0.23, it only runs every 36 hours anyway. Thoughts?
[root@preethi ~]# rpm -q gofer gofer-0.24-1.fc14.noarch [root@preethi ~]# cat /etc/gofer/agent.conf |grep url # url : The broker url. # The url has form: <transport>://<host>:<port> where # url = tcp://localhost:5672
verified [root@preethi ~]# rpm -q pulp pulp-0.0.157-1.git.1.1ea502c.fc14.noarch <jortel> the fix is in /etc/gofer/plugins/builtin.conf <jortel> url= [root@preethi ~]# cat /etc/gofer/plugins/builtin.conf [main] enabled=1 [messaging] url= uuid=
Closing with Community Release 15 pulp-0.0.223-4.