Bug 1212601 - Removing a product from a sync plan does not remove the sync schedule from the repositories in pulp
Summary: Removing a product from a sync plan does not remove the sync schedule from th...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Tazim Kolhar
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-16 18:36 UTC by Eric Helms
Modified: 2017-02-23 20:10 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-12 13:56:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 9866 0 None None None 2016-04-22 16:53:40 UTC

Description Eric Helms 2015-04-16 18:36:51 UTC
Comment 1 Eric Helms 2015-04-16 18:36:52 UTC 
Created from redmine issue http://projects.theforeman.org/issues/9866
Comment 3 Tazim Kolhar 2015-04-28 11:17:33 UTC 
hi


please provide verification steps

thanks
Comment 4 Eric Helms 2015-05-05 21:27:30 UTC 
Steps to verify:

1. Create a custom product and add a repository to it
2. Create a sync plan set for hourly, 5 minutes from now
3. Wait for repository to sync via sync plan
4. Remove sync plan from the product
5. Wait an hour or more to verify that the repository did not sync again
Comment 5 Tazim Kolhar 2015-05-06 09:34:13 UTC 
VERIFIED :

# rpm -qa  | grep foreman
ibm-hs22-02.rhts.eng.brq.redhat.com-foreman-proxy-client-1.0-1.noarch
foreman-gce-1.7.2.18-1.el7sat.noarch
foreman-postgresql-1.7.2.18-1.el7sat.noarch
foreman-compute-1.7.2.18-1.el7sat.noarch
ruby193-rubygem-foreman_discovery-2.0.0.12-1.el7sat.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.8-1.el7sat.noarch
foreman-libvirt-1.7.2.18-1.el7sat.noarch
foreman-vmware-1.7.2.18-1.el7sat.noarch
ruby193-rubygem-foreman-redhat_access-0.1.0-1.el7sat.noarch
ruby193-rubygem-foreman-tasks-0.6.12.4-1.el7sat.noarch
rubygem-hammer_cli_foreman_bootdisk-0.1.2.6-1.el7sat.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2.12-1.el7sat.noarch
ruby193-rubygem-foreman_docker-1.2.0.10-1.el7sat.noarch
rubygem-hammer_cli_foreman-0.1.4.10-1.el7sat.noarch
foreman-debug-1.7.2.18-1.el7sat.noarch
foreman-proxy-1.7.2.4-1.el7sat.noarch
ibm-hs22-02.rhts.eng.brq.redhat.com-foreman-client-1.0-1.noarch
ibm-hs22-02.rhts.eng.brq.redhat.com-foreman-proxy-1.0-2.noarch
foreman-1.7.2.18-1.el7sat.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el7sat.noarch
ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch
foreman-selinux-1.7.2.13-1.el7sat.noarch
puppet-foreman_scap_client-0.3.3-8.el7sat.noarch
foreman-ovirt-1.7.2.18-1.el7sat.noarch

steps:
1. Create a custom product and add a repository to it
2. Create a sync plan set for hourly, 5 minutes from now
3. Wait for repository to sync via sync plan
4. Remove sync plan from the product
5. the repository did not sync again
Comment 6 Bryan Kearney 2015-08-11 13:20:57 UTC 
This bug is slated to be released with Satellite 6.1.
Comment 7 Bryan Kearney 2015-08-12 13:56:56 UTC 
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.
Note You need to log in before you can comment on or make changes to this bug.