Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Based on email, it was mentioned that the following fix is required to resolve this one: bug 1198464.
If validated, we can probably mark this one as a duplicate.
Description of problem: When trying to sync to capsule, error is thrown in capsule logs. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Register capsule to satellite; create all appropriate environments on capsule 2. Attempt to sync content, i.e., hammer --username admin --password changeme capsule content synchronize --async --id 2 3. view /var/log/messages on capsule server. Actual results: Mar 3 20:31:11 cloud-qe-3 goferd: [INFO][worker-0] root:473 - connecting to rhsm-qe-2.rhq.lab.eng.bos.redhat.com:5647... Mar 3 20:31:12 cloud-qe-3 goferd: [INFO][worker-0] gofer.messaging.adapter.proton.connection:103 - connected: amqps://rhsm-qe-2.rhq.lab.eng.bos.redhat.com:5647 Mar 3 20:31:12 cloud-qe-3 goferd: [INFO][worker-0] root:493 - connected to rhsm-qe-2.rhq.lab.eng.bos.redhat.com:5647 Mar 3 20:31:12 cloud-qe-3 goferd: [INFO][worker-0] gofer.rmi.dispatcher:610 - call: Content.update() sn=1f6bf9f4-26ff-4eea-b68b-507a72f49576 data={'task_id': '7909008c-5b7f-4014-bfa0-fa5bd821bf9b', 'consumer_id': '6b887ca1-cbfd-4fd8-b573-61577e506468'} Mar 3 20:31:12 cloud-qe-3 goferd: [ERROR][worker-0] pulp.agent.lib.dispatcher:112 - handler failed Mar 3 20:31:12 cloud-qe-3 goferd: [ERROR][worker-0] pulp.agent.lib.dispatcher:112 - Traceback (most recent call last): Mar 3 20:31:12 cloud-qe-3 goferd: [ERROR][worker-0] pulp.agent.lib.dispatcher:112 - File "/usr/lib/python2.7/site-packages/pulp/agent/lib/dispatcher.py", line 108, in update Mar 3 20:31:12 cloud-qe-3 goferd: [ERROR][worker-0] pulp.agent.lib.dispatcher:112 - report = handler.update(conduit, units, dict(options)) Mar 3 20:31:12 cloud-qe-3 goferd: [ERROR][worker-0] pulp.agent.lib.dispatcher:112 - File "/usr/lib/python2.7/site-packages/pulp_node/handlers/handler.py", line 107, in update Mar 3 20:31:12 cloud-qe-3 goferd: [ERROR][worker-0] pulp.agent.lib.dispatcher:112 - strategy = find_strategy(strategy_name)() Mar 3 20:31:12 cloud-qe-3 goferd: [ERROR][worker-0] pulp.agent.lib.dispatcher:112 - File "/usr/lib/python2.7/site-packages/pulp_node/handlers/strategies.py", line 294, in find_strategy Mar 3 20:31:12 cloud-qe-3 goferd: [ERROR][worker-0] pulp.agent.lib.dispatcher:112 - raise StrategyUnsupported(name) Mar 3 20:31:12 cloud-qe-3 goferd: [ERROR][worker-0] pulp.agent.lib.dispatcher:112 - StrategyUnsupported: Handler strategy "None" not supported Expected results: Working sync. Additional info: