Description of problem: [RFE] Sync Status page - Disable 'Synchronize Now' button until atleast one repo is selected for sync. Version-Release number of selected component (if applicable): GA Snap 4 - Satellite-6.0.4-RHEL-6-20140806.0 * apr-util-ldap-1.3.9-3.el6_0.1.x86_64 * candlepin-0.9.19-1.el6_5.noarch * candlepin-scl-1-5.el6_4.noarch * candlepin-scl-quartz-2.1.5-5.el6_4.noarch * candlepin-scl-rhino-1.7R3-1.el6_4.noarch * candlepin-scl-runtime-1-5.el6_4.noarch * candlepin-selinux-0.9.19-1.el6_5.noarch * candlepin-tomcat6-0.9.19-1.el6_5.noarch * elasticsearch-0.90.10-4.el6sat.noarch * foreman-1.6.0.38-1.el6sat.noarch * foreman-compute-1.6.0.38-1.el6sat.noarch * foreman-gce-1.6.0.38-1.el6sat.noarch * foreman-libvirt-1.6.0.38-1.el6sat.noarch * foreman-ovirt-1.6.0.38-1.el6sat.noarch * foreman-postgresql-1.6.0.38-1.el6sat.noarch * foreman-proxy-1.6.0.23-1.el6sat.noarch * foreman-selinux-1.6.0.4-1.el6sat.noarch * foreman-vmware-1.6.0.38-1.el6sat.noarch * katello-1.5.0-28.el6sat.noarch * katello-ca-1.0-1.noarch * katello-certs-tools-1.5.6-1.el6sat.noarch * katello-installer-0.0.57-1.el6sat.noarch * openldap-2.4.23-34.el6_5.1.x86_64 * pulp-katello-0.3-3.el6sat.noarch * pulp-nodes-common-2.4.0-0.30.beta.el6sat.noarch * pulp-nodes-parent-2.4.0-0.30.beta.el6sat.noarch * pulp-puppet-plugins-2.4.0-0.30.beta.el6sat.noarch * pulp-puppet-tools-2.4.0-0.30.beta.el6sat.noarch * pulp-rpm-plugins-2.4.0-0.30.beta.el6sat.noarch * pulp-selinux-2.4.0-0.30.beta.el6sat.noarch * pulp-server-2.4.0-0.30.beta.el6sat.noarch * python-ldap-2.3.10-1.el6.x86_64 * ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch * ruby193-rubygem-runcible-1.1.0-2.el6sat.noarch * sssd-ldap-1.11.5.1-3.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. Navigate to Content -> Sync Status page 2. Without selecting any repo, click 'Synchronize Now' Actual results: Nothing happens Expected results: Disable 'Synchronize Now' button until atleast one repo is selected for sync. Additional info:
Created redmine issue http://projects.theforeman.org/issues/13943 from this bug
Moving to POST since upstream bug http://projects.theforeman.org/issues/13943 has been closed ------------- Adam Ruzicka Applied in changeset commit:katello|774e9f922ed095bb336bdd08d0752649976212a1.
VERIFIED: # rpm -qa | grep foreman tfm-rubygem-foreman_gutterball-0.0.1-6.el7sat.noarch ibm-x3550m3-09.lab.eng.brq.redhat.com-foreman-proxy-1.0-1.noarch foreman-selinux-1.11.0-1.el7sat.noarch tfm-rubygem-foreman_theme_satellite-0.1.2-1.el7sat.noarch tfm-rubygem-hammer_cli_foreman-0.5.1.2-1.el7sat.noarch tfm-rubygem-foreman_openscap-0.5.3.0-1.el7sat.noarch ibm-x3550m3-09.lab.eng.brq.redhat.com-foreman-client-1.0-1.noarch tfm-rubygem-hammer_cli_foreman_tasks-0.0.10-2.el7sat.noarch foreman-compute-1.11.0.6-1.el7sat.noarch tfm-rubygem-foreman_bootdisk-6.1.0-1.el7sat.noarch foreman-gce-1.11.0.6-1.el7sat.noarch foreman-postgresql-1.11.0.6-1.el7sat.noarch foreman-proxy-1.11.0.1-1.el7sat.noarch foreman-installer-1.11.0.0-1.el7sat.noarch tfm-rubygem-foreman-tasks-0.7.14.1-1.el7sat.noarch foreman-vmware-1.11.0.6-1.el7sat.noarch foreman-debug-1.11.0.6-1.el7sat.noarch tfm-rubygem-foreman_hooks-0.3.9-2.el7sat.noarch foreman-discovery-image-3.0.5-3.el7sat.noarch tfm-rubygem-hammer_cli_foreman_bootdisk-0.1.3-4.el7sat.noarch foreman-1.11.0.6-1.el7sat.noarch foreman-ovirt-1.11.0.6-1.el7sat.noarch foreman-libvirt-1.11.0.6-1.el7sat.noarch tfm-rubygem-foreman_discovery-5.0.0.1-1.el7sat.noarch foreman-installer-katello-3.0.0.3-1.el7sat.noarch tfm-rubygem-hammer_cli_foreman_docker-0.0.3-5.el7sat.noarch tfm-rubygem-foreman_docker-2.0.1-1.el7sat.noarch tfm-rubygem-foreman-redhat_access-1.0.1-1.el7sat.noarch ibm-x3550m3-09.lab.eng.brq.redhat.com-foreman-proxy-client-1.0-1.noarch puppet-foreman_scap_client-0.3.3-10.el7sat.noarch tfm-rubygem-foreman_remote_execution-0.3.0.1-1.el7sat.noarch Steps: 1. Navigate to Content -> Sync Status page 2. Without selecting any repo, click 'Sync Now' Sync Now is disabled if no repo is selected
Created attachment 1138913 [details] Sync Now if no repo is selected
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/RHBA-2016:1501