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 801580 - Updating sync plan does not update associated product's (repo's) sync schedule
Summary: Updating sync plan does not update associated product's (repo's) sync schedule
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: Petr Chalupa
QA Contact: Og Maciel
URL:
Whiteboard:
Depends On:
Blocks: 828308
TreeView+ depends on / blocked
 
Reported: 2012-03-08 22:00 UTC by Justin Sherrill
Modified: 2019-09-26 15:54 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Changing a sync plan does not propagate changes to the associated products' sync plans. The plan retains the original sync plan's details. This fix updates the associated products' sync plans when changes are made. All associated sync plans' details should appropriately update.
Clone Of:
: 828308 (view as bug list)
Environment:
Last Closed: 2012-12-04 19:42:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:1543 0 normal SHIPPED_LIVE Important: CloudForms System Engine 1.1 update 2012-12-05 00:39:57 UTC

Description Justin Sherrill 2012-03-08 22:00:40 UTC 
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.
Comment 1 Petr Chalupa 2012-03-15 16:21:07 UTC 
fixed in 15fabee5062f3196f50e471a296a2f97ddfa11eb
Comment 4 Petr Chalupa 2012-06-14 09:46:30 UTC 
there was still a bug, fixed in aa5a22b68265dbc201db6d7d64e31aeaeb88c0e8 for 
https://bugzilla.redhat.com/show_bug.cgi?id=828308
Comment 6 Og Maciel 2012-09-17 22:14:51 UTC 
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
Comment 7 Og Maciel 2012-09-17 22:15:47 UTC 
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
Comment 9 errata-xmlrpc 2012-12-04 19:42:44 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.