Description of problem: save button does not enable when creating a new sync plan Version-Release number of selected component (if applicable): Nightly Oct 10, 2014 * apr-util-ldap-1.3.9-3.el6_0.1.x86_64 * candlepin-0.9.32-1.el6.noarch * candlepin-common-1.0.8-1.el6.noarch * candlepin-selinux-0.9.32-1.el6.noarch * candlepin-tomcat6-0.9.32-1.el6.noarch * elasticsearch-0.90.10-7.el6.noarch * foreman-1.7.0-0.develop.201410091913git35b6fb9.el6.noarch * foreman-compute-1.7.0-0.develop.201410091913git35b6fb9.el6.noarch * foreman-gce-1.7.0-0.develop.201410091913git35b6fb9.el6.noarch * foreman-libvirt-1.7.0-0.develop.201410091913git35b6fb9.el6.noarch * foreman-ovirt-1.7.0-0.develop.201410091913git35b6fb9.el6.noarch * foreman-postgresql-1.7.0-0.develop.201410091913git35b6fb9.el6.noarch * foreman-proxy-1.7.0-0.develop.201410081229git52f0bac.el6.noarch * foreman-release-1.7.0-0.develop.201410091913git35b6fb9.el6.noarch * foreman-selinux-1.7.0-0.develop.201409301113git2f345de.el6.noarch * foreman-vmware-1.7.0-0.develop.201410091913git35b6fb9.el6.noarch * katello-2.1.0-1.201410091751gitc9c45c1.el6.noarch * katello-certs-tools-2.0.1-1.el6.noarch * katello-default-ca-1.0-1.noarch * katello-installer-2.1.0-1.201410021645git304e036.el6.noarch * katello-repos-2.1.1-1.el6.noarch * katello-server-ca-1.0-1.noarch * openldap-2.4.23-32.el6_4.1.x86_64 * pulp-docker-plugins-0.2.1-0.2.beta.el6.noarch * pulp-katello-0.3-3.el6.noarch * pulp-nodes-common-2.5.0-0.7.beta.el6.noarch * pulp-nodes-parent-2.5.0-0.7.beta.el6.noarch * pulp-puppet-plugins-2.5.0-0.7.beta.el6.noarch * pulp-puppet-tools-2.5.0-0.7.beta.el6.noarch * pulp-rpm-plugins-2.5.0-0.7.beta.el6.noarch * pulp-selinux-2.5.0-0.7.beta.el6.noarch * pulp-server-2.5.0-0.7.beta.el6.noarch * python-ldap-2.3.10-1.el6.x86_64 * ruby193-rubygem-ldap_fluff-0.3.1-1.el6.noarch * ruby193-rubygem-net-ldap-0.3.1-2.el6.noarch * ruby193-rubygem-runcible-1.2.0-1.el6.noarch How reproducible: Always Steps to Reproduce: 1. Create a sync plan 2. Enter a sync plan name 3. Actual results: Save button is disabled Cancel button does not work Expected results: Save button should be enabled to save the sync plan Additional info:
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
Connecting redmine issue http://projects.theforeman.org/issues/7919 from this bug
PR: https://github.com/Katello/katello/pull/4737
Moving to POST since upstream bug http://projects.theforeman.org/issues/7919 has been closed ------------- Walden Raines Applied in changeset commit:katello|5b2fc29f1c1c035b95f16b5461098e13ffd3a585.
VERIFIED *** This bug is verified in upstream. This fix should eventually land in future downstream builds *** Version Tested: # rpm -qa | grep foreman ruby193-rubygem-foreman_hooks-0.3.7-2.el7.noarch rubygem-hammer_cli_foreman_tasks-0.0.3-2.201409091410git163c264.git.0.988ca80.el7.noarch ruby193-rubygem-foreman_abrt-0.0.4-1.el7.noarch ruby193-rubygem-foreman_docker-0.2.0-2.el7.noarch ruby193-rubygem-foreman_bootdisk-4.0.2-1.el7.noarch rubygem-hammer_cli_foreman-0.1.3-1.201411121216git9381fc5.el7.noarch hp-dl380pgen8-02-vm-6.lab.bos.redhat.com-foreman-client-1.0-1.noarch foreman-1.8.0-0.develop.201411201054gitbe4602e.el7.noarch foreman-ovirt-1.8.0-0.develop.201411201054gitbe4602e.el7.noarch ruby193-rubygem-foreman-tasks-0.6.9-1.el7.noarch ruby193-rubygem-foreman_discovery-1.4.0-2.el7.noarch foreman-postgresql-1.8.0-0.develop.201411201054gitbe4602e.el7.noarch foreman-compute-1.8.0-0.develop.201411201054gitbe4602e.el7.noarch foreman-gce-1.8.0-0.develop.201411201054gitbe4602e.el7.noarch foreman-libvirt-1.8.0-0.develop.201411201054gitbe4602e.el7.noarch foreman-vmware-1.8.0-0.develop.201411201054gitbe4602e.el7.noarch foreman-selinux-1.8.0-0.develop.201410280941git10de1c5.el7.noarch foreman-proxy-1.8.0-0.develop.201411121327gitab6edc2.el7.noarch hp-dl380pgen8-02-vm-6.lab.bos.redhat.com-foreman-proxy-1.0-1.noarch foreman-release-1.8.0-0.develop.201411201054gitbe4602e.el7.noarch Save button enabled when we add sync plan name
This bug is slated to be released with Satellite 6.1.
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-2015:1592