Description of problem: Once I create a sync plan in Web UI, I can't change "Next Sync" / sync-date there. So I can't apply changes like "let synchronize with CDN at 3am, not at 5am every day". As hammer CLI allows that change via sync-plan update --sync-date option, it is just WebUI lacking the ability to edit. Version-Release number of selected component (if applicable): Satellite 6.0.6 How reproducible: 100% Steps to Reproduce: 1. Create a sync plan via WebUI 2. Try to edit it. Actual results: You can change Name, Description and Interval, but not either Start Date or Next Sync. Expected results: You can change Name, Description, Interval and also Next Sync. Once the Next Sync is changed, the next synchronization is really executed at that time and not at the original time. Additional info: Workaround: use hammer CLI.
*** Bug 1195836 has been marked as a duplicate of this bug. ***
Created redmine issue http://projects.theforeman.org/issues/10140 from this bug
PR: https://github.com/Katello/katello/pull/5177
Moving to POST since upstream bug http://projects.theforeman.org/issues/10140 has been closed ------------- Walden Raines Applied in changeset commit:katello|f614d6b6ef23dac73580c46ddbb13ab9cc48ef77.
FAILEDQA: # rpm -qa | grep foreman foreman-libvirt-1.7.2.17-1.el6_6sat.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.10-1.el6_6sat.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el6_6sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.3-1.el6_6sat.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.5-1.el6_6sat.noarch foreman-postgresql-1.7.2.17-1.el6_6sat.noarch foreman-debug-1.7.2.17-1.el6_6sat.noarch foreman-1.7.2.17-1.el6_6sat.noarch foreman-ovirt-1.7.2.17-1.el6_6sat.noarch ruby193-rubygem-foreman-tasks-0.6.12.3-1.el6_6sat.noarch foreman-proxy-1.7.2.4-1.el6_6sat.noarch qe-sat6-rhel66.usersys.redhat.com-foreman-client-1.0-1.noarch qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-client-1.0-1.noarch foreman-selinux-1.7.2.13-1.el6_6sat.noarch rubygem-hammer_cli_foreman-0.1.4.9-1.el6_6sat.noarch foreman-compute-1.7.2.17-1.el6_6sat.noarch foreman-vmware-1.7.2.17-1.el6_6sat.noarch ruby193-rubygem-foreman-redhat_access-0.1.0-1.el6_6sat.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el6_6sat.noarch qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-1.0-2.noarch ruby193-rubygem-foreman_docker-1.2.0.9-1.el6_6sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.7-1.el6_6sat.noarch foreman-gce-1.7.2.17-1.el6_6sat.noarch ruby193-rubygem-foreman_discovery-2.0.0.9-1.el6_6sat.noarch steps: 1. Create a sync plan via WebUI 2. Try to edit it. screenshot attached
Created attachment 1018373 [details] sync plan edit next sync
Nothing for me to do here, not sure why this didn't make it in the latest build. It seems to have been cherry-picked correctly into the 6.1 repo.
This was due to SNAP1 missing the build of katello, back ON_QA now. Sorry for the time waste.
VERIFIED : # rpm -qa | grep foreman ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch foreman-selinux-1.7.2.13-1.el7sat.noarch ruby193-rubygem-foreman_docker-1.2.0.9-1.el7sat.noarch ruby193-rubygem-foreman-tasks-0.6.12.3-1.el7sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.3-1.el7sat.noarch foreman-debug-1.7.2.17-1.el7sat.noarch foreman-libvirt-1.7.2.17-1.el7sat.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.10-1.el7sat.noarch foreman-compute-1.7.2.17-1.el7sat.noarch foreman-ovirt-1.7.2.17-1.el7sat.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.5-1.el7sat.noarch foreman-postgresql-1.7.2.17-1.el7sat.noarch qe-sat6-rhel71.usersys.redhat.com-foreman-client-1.0-1.noarch qe-sat6-rhel71.usersys.redhat.com-foreman-proxy-1.0-1.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch foreman-1.7.2.17-1.el7sat.noarch foreman-gce-1.7.2.17-1.el7sat.noarch ruby193-rubygem-foreman_discovery-2.0.0.9-1.el7sat.noarch rubygem-hammer_cli_foreman-0.1.4.9-1.el7sat.noarch foreman-vmware-1.7.2.17-1.el7sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.7-1.el7sat.noarch foreman-proxy-1.7.2.4-1.el7sat.noarch qe-sat6-rhel71.usersys.redhat.com-foreman-proxy-client-1.0-1.noarch ruby193-rubygem-foreman-redhat_access-0.1.0-1.el7sat.noarch steps 1. Create a sync plan via WebUI 2. Try to edit it. screenshot attached
Created attachment 1019285 [details] sync plan edit next sync
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.