Bug 882428
Summary: | Creating a scheduled sync with a feed URL that is shared with another repo that is currently syncing causes an unserializable JSON TypeError | ||
---|---|---|---|
Product: | [Retired] Pulp | Reporter: | Randy Barlow <rbarlow> |
Component: | async/tasks | Assignee: | Jason Connor <jconnor> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Preethi Thomas <pthomas> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 2.0.6 | CC: | jason.dobies, mmccune, skarmark |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-01-07 14:09:36 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Randy Barlow
2012-11-30 22:37:21 UTC
I don't even know where to start on this one. Can you reliably reproduce it? I went in to look at it today, and I found something kind of interesting: $ pulp-admin rpm repo list +----------------------------------------------------------------------+ RPM Repositories +----------------------------------------------------------------------+ Id: pulp-rhel6-i386 Display Name: pulp-rhel6-i386 Description: None Content Unit Count: 36 Id: rhel6-i386 Display Name: rhel6-i386 Description: None Content Unit Count: 0 Id: rhel6-server-i386 Display Name: rhel6-server-i386 Description: None Content Unit Count: 8284 The bottom two repos there are the two that were causing this issue. The strange thing is that the one that was syncing first is the one that now reports having 0 units, and the second one was the one that caused the issue when I added the sync schedule. $ pulp-admin rpm repo sync schedules list --repo-id=rhel6-server-i386 +----------------------------------------------------------------------+ Schedules +----------------------------------------------------------------------+ Schedule: 2012-11-30T22:10:00Z/P1M Id: 50b92e61e5147d0bbc0028a2 Enabled: True Last Run: 2012-12-30T22:10:00Z Next Run: 2012-12-30T22:10:00Z I haven't tried to reproduce it today, but I will put that on my todo list. I know what's going here. The result from a meta usage of the coordinator in the scheduler is generating the scheduled call requests. These call requests are being reported as the result of the meta call request and are not serializable. Randy's observation in comment 2, however, isn't relavent. (In reply to comment #3) > Randy's observation in comment 2, however, isn't relavent. Should we report that as a separate bug then? *** Bug 880094 has been marked as a duplicate of this bug. *** Added a flag to call report to toggle the obfuscation of call's result. Fix in branch: jconnor-result-reporting-bugs Merged into pulp-2.0 in revision: a210efcff37315a8b04876c12ea179aba958900e build: 2.0.6-0.12.beta verified 1. Created 2 repos same feed url 2. Sync one 3. Create a sync schedule on other 4. Run tasks list [root@preethi ~]# pulp-admin tasks list +----------------------------------------------------------------------+ Tasks +----------------------------------------------------------------------+ Operations: create_sync_schedule Resources: fedora17-1 (repository), yum_importer (repository_importer) State: Successful Start Time: Unstarted Finish Time: 2012-12-10T13:55:26Z Result: 50c5e9cd758cc94b56000132 Task Id: 89ce6115-384b-42ce-92ac-15c4e0d313a0 Operations: sync Resources: fedora17 (repository) State: Running Start Time: 2012-12-10T13:52:48Z Finish Time: Incomplete Result: Incomplete Task Id: e582b358-7770-4474-bd44-0787e2b7245a Operations: auto_publish, publish Resources: fedora17 (repository) State: Waiting Start Time: Unstarted Finish Time: Incomplete Result: Incomplete Task Id: e510e5ca-31e0-4cb8-8225-5cc6fded4433 Pulp 2.0 released. |