Changing a sync plan to enabled=false does not actually disable the sync plan in pulp.
Created from redmine issue http://projects.theforeman.org/issues/9818
Moving to POST since upstream bug http://projects.theforeman.org/issues/9818 has been closed ------------- Eric Helms Applied in changeset commit:katello|d69624f9dc78a4f71fef680a513a3a47e2bb1193.
hi please provide verification steps thanks
Steps to verify: 1. Create a sync plan with an hourly interval 2. Add a product with repository to the sync plan 3. Wait for sync to occur 4. Edit the sync plan from the UI and uncheck enabled 5. Note that it should show no 'Next Sync' time 6. Wait for another hour to verify that a sync does not occur
VERIFIED : rpm -qa | grep foreman foreman-gce-1.7.2.17-1.el7sat.noarch foreman-debug-1.7.2.17-1.el7sat.noarch foreman-discovery-image-2.1.0-20.el7sat.noarch foreman-compute-1.7.2.17-1.el7sat.noarch foreman-ovirt-1.7.2.17-1.el7sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.3-1.el7sat.noarch ruby193-rubygem-foreman_docker-1.2.0.9-1.el7sat.noarch ruby193-rubygem-foreman-redhat_access-0.1.0-1.el7sat.noarch ruby193-rubygem-foreman-tasks-0.6.12.3-1.el7sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.7-1.el7sat.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.10-1.el7sat.noarch foreman-proxy-1.7.2.4-1.el7sat.noarch cloud-qe-9.idmqe.lab.eng.bos.redhat.com-foreman-client-1.0-1.noarch cloud-qe-9.idmqe.lab.eng.bos.redhat.com-foreman-proxy-1.0-2.noarch foreman-vmware-1.7.2.17-1.el7sat.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch rubygem-hammer_cli_foreman-0.1.4.9-1.el7sat.noarch foreman-libvirt-1.7.2.17-1.el7sat.noarch foreman-selinux-1.7.2.13-1.el7sat.noarch foreman-postgresql-1.7.2.17-1.el7sat.noarch cloud-qe-9.idmqe.lab.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch foreman-1.7.2.17-1.el7sat.noarch ruby193-rubygem-foreman_discovery-2.0.0.9-1.el7sat.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.5-1.el7sat.noarch steps; 1. Create a sync plan with an hourly interval 2. Add a product with repository to the sync plan 3. Wait for sync to occur 4. Edit the sync plan from the UI and uncheck enabled 5. Note that it should show no 'Next Sync' time 6. Wait for another hour to verify that a sync does not occur the 'Next Sync' time is not shown sync does not occur
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.