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 from redmine issue http://projects.theforeman.org/issues/8984

To Test:

1) Create a product and repository
2) Create a sync plan (e.g. hourly starting 10 minutes from creation)
3) Add the product to the sync plan
4) Wait to see the product syncs via sync plan
5) Delete the sync plan
6) Wait and see if product syncs on the schedule (~1 hr later)

The highlighted lines can be put into the Rakefile and ran to report and detect sync schedules that still exist in Pulp:

https://gist.github.com/ehelms/52405ed3e75ec54ed91f#file-gistfile1-txt-L1-L14

Verified by QE on version Satellite-6.1.0-RHEL-7-20150324.0

This bug is slated to be released with Satellite 6.1.

This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.