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.
Created attachment 650553[details]
katello debug output
Description of problem:
After importing a manifest and scheduling a sync for Red Hat Enterprise Linux 6 Server RPMs x86_64 6.3, the sync fails.
Version-Release number of selected component (if applicable):
Will attach katello debug output.
How reproducible:
Unknown
Steps to Reproduce:
1. Import manifest from hosted, employee sub in my case.
2. Sync Red Hat Enterprise Linux 6 Server RPMs x86_64 6.3
Actual results:
Sync eventually fails. (after some time)
"Size (Packages)" column was populated with numbers during the run, but after failure reads 0 bytes (0).
Notification for the failure does not have a link to additional info like my other repo that failed to sync. (see bug #878679)
Expected results:
Success. :)
Additional info:
This stack trace in pulp.log looked like a possible culprit but this was not visible in the UI notifications.
2012-11-23 11:27:10,079 13221:140118228518656: pulp.server.api.repo_sync:INFO: repo_sync:286 Sync on ACME_Corporation-Red_Hat_Enterprise_Linux_Server-Red_Hat_Enterprise_Linux_6_Server_-_Supplementary_RPMs_x86_64_6_3 returned 311 packages, 65 errata in 343.699318171 seconds
2012-11-23 11:27:10,088 13221:140118228518656: pulp.server.api.repo_sync:INFO: repo_sync:297 0 old packages to process, 0 new packages to process
2012-11-23 11:27:10,088 13221:140118228518656: pulp.server.api.repo_sync:INFO: repo_sync:299 Removing 0 old packages
2012-11-23 11:27:10,095 13221:140118228518656: pulp.server.api.repo_sync:INFO: repo_sync:305 Adding 0 new packages
2012-11-23 11:27:10,141 13221:140118228518656: pulp.server.api.repo_sync:INFO: repo_sync:314 Examining 65 errata from repo ACME_Corporation-Red_Hat_Enterprise_Linux_Server-Red_Hat_Enterprise_Linux_6_Server_-_Supplementary_RPMs_x86_64_6_3
2012-11-23 11:27:10,180 13221:140118228518656: pulp.server.api.repo_sync:INFO: repo_sync:318 Removing 0 old errata from repo ACME_Corporation-Red_Hat_Enterprise_Linux_Server-Red_Hat_Enterprise_Linux_6_Server_-_Supplementary_RPMs_x86_64_6_3
2012-11-23 11:27:10,224 13221:140118228518656: pulp.server.api.repo_sync:INFO: repo_sync:327 Adding 0 new errata to repo ACME_Corporation-Red_Hat_Enterprise_Linux_Server-Red_Hat_Enterprise_Linux_6_Server_-_Supplementary_RPMs_x86_64_6_3
2012-11-23 11:27:10,241 13221:140118228518656: pulp.server.tasking.task:INFO: task:454 Task succeeded: Task bd97dc3a-357d-11e2-a330-525400c6b24f: _sync(ACME_Corporation-Red_Hat_Enterprise_Linux_Server-Red_Hat_Enterprise_Linux_6_Server_-_Supplementary_RPMs_x86_64_6_3, synchronizer=<pulp.server.api.synchronizers.YumSynchronizer object at 0x7f6fbca73150>, skip={}, max_speed=None, threads=4, progress_callback=<bound method RepoSyncTask.progress_callback of <pulp.server.api.repo_sync_task.RepoSyncTask object at 0x7f6fbc89f190>>)
2012-11-23 12:02:31,838 13221:140117964470016: pulp.server.webservices.controllers.decorators:ERROR: decorators:52 Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/pulp/server/webservices/controllers/decorators.py", line 48, in report_error
return method(self, *args, **kwargs)
File "/usr/lib/python2.6/site-packages/pulp/server/webservices/controllers/decorators.py", line 127, in _auth_decorator
value = method(self, *args, **kwargs)
File "/usr/lib/python2.6/site-packages/pulp/server/webservices/controllers/repositories.py", line 2163, in GET
return self.ok(task_infos)
File "/usr/lib/python2.6/site-packages/pulp/server/webservices/controllers/base.py", line 156, in ok
return self._output(data)
File "/usr/lib/python2.6/site-packages/pulp/server/webservices/controllers/base.py", line 131, in _output
body = json.dumps(data, default=json_util.default)
File "/usr/lib64/python2.6/site-packages/simplejson/__init__.py", line 237, in dumps
**kw).encode(obj)
File "/usr/lib64/python2.6/site-packages/simplejson/encoder.py", line 200, in encode
chunks = self.iterencode(o, _one_shot=True)
File "/usr/lib64/python2.6/site-packages/simplejson/encoder.py", line 260, in iterencode
return _iterencode(o, 0)
File "/usr/lib64/python2.6/site-packages/bson/json_util.py", line 133, in default
raise TypeError("%r is not JSON serializable" % obj)
TypeError: error(23, 'Failed writing body (0 != 15998)') is not JSON serializable
2012-11-23 12:08:41,082 13221:140118006429440: pulp.server.api.synchronizers:INFO: synchronizers:795 YumSynchronizer reported 8145 successes, 6744 downloads, 570 errors
2012-11-23 12:08:46,957 13221:140118006429440: pulp.server.tasking.task:ERROR: task:472 Task failed: Task 775107ee-34d5-11e2-9565-525400c6b24f: _sync(A
Was running a non-official RHEL 6.4 build in case this is relevant.
This bug was closed because of a lack of activity. If you feel this bug should be reconsidered for attention please feel free to re-open the bug with a comment stating why it should be reconsidered.