Red Hat Bugzilla – Bug 1195972
Content View: Cannot actually click checkbox for promoting
Last modified: 2017-02-23 15:26:29 EST
Description of problem: Cannot click checkbox for an environment when trying to promote. User can click text or anywhere else in the environment div, but the checkbox itself is nonresponsive. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create a content view and add repos. 2. Attempt to promote content to a new env; click the checkbox to try and and select the env. Actual results: Cannot click/toggle the checkbox!! The workaround is to click the text, or somewhere else in the div for the env name. but click the checkbox itself doesn't work Expected results: User can actually click the checkbox. Additional info:
Version: Satellite-6.1.0-RHEL-7-20150224.0
What browser and version were you using for this test?
Created redmine issue http://projects.theforeman.org/issues/9549 from this bug
@eric it was both chrome and FF. Raising this to high per QE discussion that usability issues (that might turn into customer calls) should have a raised profile.
PR: https://github.com/Katello/bastion/pull/49
Moving to POST since upstream bug http://projects.theforeman.org/issues/9549 has been closed ------------- Walden Raines Applied in changeset commit:bastion|c7997649e77a968949ab55fef1f02a98d62697c1.
VERIFIED: # rpm -qa | grep foreman foreman-1.7.2.8-1.el6_6sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.2-1.el6_6sat.noarch foreman-compute-1.7.2.8-1.el6_6sat.noarch ruby193-rubygem-foreman_docker-1.2.0.2-1.el6_6sat.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el6_6sat.noarch ruby193-rubygem-foreman-tasks-0.6.12.1-1.el6_6sat.noarch foreman-proxy-1.7.2.3-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 rubygem-hammer_cli_foreman_bootdisk-0.1.2.5-1.el6_6sat.noarch foreman-vmware-1.7.2.8-1.el6_6sat.noarch foreman-libvirt-1.7.2.8-1.el6_6sat.noarch ruby193-rubygem-foreman_abrt-0.0.5-2.el6_6sat.noarch qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-1.0-2.noarch rubygem-hammer_cli_foreman-0.1.4.6-1.el6_6sat.noarch foreman-selinux-1.7.2.8-1.el6_6sat.noarch foreman-debug-1.7.2.8-1.el6_6sat.noarch foreman-gce-1.7.2.8-1.el6_6sat.noarch ruby193-rubygem-foreman-redhat_access-0.0.8-2.el6_6sat.noarch ruby193-rubygem-foreman_discovery-2.0.0.5-1.el6_6sat.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el6_6sat.noarch foreman-postgresql-1.7.2.8-1.el6_6sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.3-1.el6_6sat.noarch foreman-ovirt-1.7.2.8-1.el6_6sat.noarch User can actually click the checkbox.
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