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.
Description of problem:
When I delete a sync plan with associated product(s) and repo(s), the pulp repos are still synced underneath like the plan would still exist.
The cause is, katello does not delete the sync plan but updates it, since pulp_rest debugs show:
2018-06-11 13:40:29 [katello/pulp_rest] [D] RestClient.put "https://pmoravec-sat63.gsslab.brq2.redhat.com/pulp/api/v2/repositories/a89a3c32-9c85-40e8-b22c-0cf3411911be/importers/yum_importer/schedules/sync/5b1ce0b3a0ad7a17858344d9/", "{\"schedule\":\"2018-06-11T14:00:00+02:00/PT1H\",\"enabled\":true}", "Accept"=>"*/*; q=0.5, application/xml", "Accept-Encoding"=>"gzip, deflate", "Content-Length"=>"60", "accept"=>"application/json", "content_type"=>"application/json"
See e.g. enabled:true. Rather DELETE op per https://docs.pulpproject.org/dev-guide/integration/rest-api/repo/sync.html#deleting-a-scheduled-sync should be used.
And pulp mongo_database really still has a record in scheduled_calls collection.
Even removing a sync plan that has not been executed is affected the same.
Version-Release number of selected component (if applicable):
Sat 6.3.1
tfm-rubygem-katello-3.4.5.64-1.el7sat.noarch
How reproducible:
100%
Steps to Reproduce:
1. Create a sync plan, add some product there
2. Delete the sync plan (even before it is executed for the 1st time)
3. Create a sync plan, add some product there, wait for its 1st (or 2nd or even more, if patient) execution
4. Delete the sync plan
5. Check on next sync plans expected execution if underlying repos will be synced / Monitor -> Tasks will have " Scheduled Synchronization repository .." tasks
Actual results:
5. Both sync plans from 1 and 3 steps are still executed, despite they have been deleted.
Expected results:
5. no further execution of sync plans after their removal
Additional info:
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.
https://access.redhat.com/errata/RHSA-2018:2927