Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 787870 - Clients subscriptions never updated via katello-agent
Summary: Clients subscriptions never updated via katello-agent
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: katello-agent
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: katello-blockers
TreeView+ depends on / blocked
 
Reported: 2012-02-06 23:24 UTC by Jeff Weiss
Modified: 2014-11-09 22:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-07 16:03:01 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jeff Weiss 2012-02-06 23:24:18 UTC 
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".
Comment 1 Jeff Weiss 2012-02-07 16:03:01 UTC 
This is not intended to work for v1.
Note You need to log in before you can comment on or make changes to this bug.