Red Hat Bugzilla – Bug 801580
Updating sync plan does not update associated product's (repo's) sync schedule
Last modified: 2015-05-04 21:30:46 EDT
Description of problem: Sync plans are linked to products, but updating a sync plan associated to a product does not reflect in pulp. Re-associating the sync plan to the product will update its true sync schedule. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create a sync plan for 1:00 pm 2. Associate sync plan to product Foo 3. List repos for Foo with pulp-admin and see Sync Schedules for 1:00 pm 4. Change sync plan to 4:00 pm 5. List repos for Foo and look at sync schedules. Actual results: Sync Schedules are not updated in the affected repos (they still say 1:00 pm). Expected results: They should be. this appears to be a backend/orchestration issue.
fixed in 15fabee5062f3196f50e471a296a2f97ddfa11eb
there was still a bug, fixed in aa5a22b68265dbc201db6d7d64e31aeaeb88c0e8 for https://bugzilla.redhat.com/show_bug.cgi?id=828308
When scheduled for 13:00: Task: 2fb13b85-0111-11e2-b15b-52540070565e Job: None Scheduler: interval Call: _sync Arguments: Lenovo-Chrome-google-chrome-x86_64 State: waiting Start time: None Finish time: None Scheduled time: 2012-09-18T17:00:00Z Result: None Exception: None Traceback: None Task: 2f7f0740-0111-11e2-b012-52540070565e Job: None Scheduler: interval Call: _sync Arguments: Lenovo-Chrome-google-chrome-32bit State: waiting Start time: None Finish time: None Scheduled time: 2012-09-18T17:00:00Z Result: None Exception: None Traceback: None When changed schedule to 16:00: Task: 6b13fa4a-0111-11e2-b68b-52540070565e Job: None Scheduler: interval Call: _sync Arguments: Lenovo-Chrome-google-chrome-x86_64 State: waiting Start time: None Finish time: None Scheduled time: 2012-09-18T20:00:00Z Result: None Exception: None Traceback: None Task: 6ae41eb8-0111-11e2-b552-52540070565e Job: None Scheduler: interval Call: _sync Arguments: Lenovo-Chrome-google-chrome-32bit State: waiting Start time: None Finish time: None Scheduled time: 2012-09-18T20:00:00Z Result: None Exception: None Traceback: None
Verified using: * candlepin-0.7.8-1.el6cf.noarch * candlepin-selinux-0.7.8-1.el6cf.noarch * candlepin-tomcat6-0.7.8-1.el6cf.noarch * katello-1.1.12-7.el6cf.noarch * katello-all-1.1.12-7.el6cf.noarch * katello-candlepin-cert-key-pair-1.0-1.noarch * katello-certs-tools-1.1.8-1.el6cf.noarch * katello-cli-1.1.8-4.el6cf.noarch * katello-cli-common-1.1.8-4.el6cf.noarch * katello-common-1.1.12-7.el6cf.noarch * katello-configure-1.1.9-3.el6cf.noarch * katello-glue-candlepin-1.1.12-7.el6cf.noarch * katello-glue-pulp-1.1.12-7.el6cf.noarch * katello-qpid-broker-key-pair-1.0-1.noarch * katello-qpid-client-key-pair-1.0-1.noarch * katello-selinux-1.1.1-1.el6cf.noarch * pulp-1.1.12-1.el6cf.noarch * pulp-common-1.1.12-1.el6cf.noarch * pulp-selinux-server-1.1.12-1.el6cf.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2012-1543.html