Description of problem:


Version-Release number of selected component (if applicable):
drop6-build2

How reproducible:
always

Steps to Reproduce:
1. Install katello-agent on a client, start the agent "service goferd start"
2. Register the client with an activation key
3. On the katello server, subscribe the system to a product
4. tail the log of the agent to make sure it's connected:

[root@katello-client1 ca]# tail -f /var/log/gofer/agent.log clientcert=/etc/pki/consumer/bundle.pem
2012-02-06 17:50:34,802 [INFO][katelloplugin-monitor] update() @ main.py:102 - uuid="49f5a099-536c-419c-9a22-940d42041280", attached
2012-02-06 17:50:34,802 [INFO][49f5a099-536c-419c-9a22-940d42041280] connect() @ broker.py:100 - connecting:
{katello-ci-rhel62.usersys.redhat.com:5672}:
transport=TCP
host=katello-ci-rhel62.usersys.redhat.com
port=5672
cacert=/etc/rhsm/ca/candlepin-local.pem
clientcert=/etc/pki/consumer/bundle.pem
2012-02-06 17:50:35,377 [INFO][49f5a099-536c-419c-9a22-940d42041280] connect() @ broker.py:103 - {katello-ci-rhel62.usersys.redhat.com:5672} connected to AMQP
  
Actual results:
client is never subscribed

Expected results:
client is subscribed, agent receives commands

Additional info:
Doesn't matter what you do on the server, client is not updated.  Client DOES get updates if you run "subscription-manager refresh".