Red Hat Bugzilla – Bug 1191216
Config Group > Classes difficult to navigate and select
Last modified: 2017-02-23 15:33:29 EST
Created attachment 990187 [details] Config Groups Classes Description of problem: Configure > Config groups: The icons next to the Available Class category are hard to see what they're trying to represent, since they're so small. They also don't change state once they've been clicked. They always stay as a + icon. Normally you click a + to expand it, and then click - to collapse it. Doing a flat list that has a lot of classes causes a lot of scrolling. Version-Release number of selected component (if applicable): 6.0.7 How reproducible: N/A Steps to Reproduce: 1. Navigate to Configure > Config Groups 2. Select an available Config Group 3. On the right window pane there are Available Classes to choose Actual results: Poor UI experience. Expected results: Better UI navigation when selecting classes for Config Groups. Additional info: Screen shot attached.
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/9335 from this bug
fixed upstream: https://github.com/theforeman/foreman/commit/ded38d14feb05301ae4542649ad951ac765258e4
VERIFIED : # rpm -qa | grep foreman foreman-postgresql-1.7.2.14-1.el6_6sat.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.5-1.el6_6sat.noarch foreman-gce-1.7.2.14-1.el6_6sat.noarch ruby193-rubygem-foreman-tasks-0.6.12.3-1.el6_6sat.noarch rubygem-hammer_cli_foreman-0.1.4.7-1.el6_6sat.noarch foreman-compute-1.7.2.14-1.el6_6sat.noarch ruby193-rubygem-foreman-redhat_access-0.1.0-1.el6_6sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.4-1.el6_6sat.noarch foreman-selinux-1.7.2.13-1.el6_6sat.noarch foreman-libvirt-1.7.2.14-1.el6_6sat.noarch foreman-ovirt-1.7.2.14-1.el6_6sat.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.10-1.el6_6sat.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el6_6sat.noarch foreman-debug-1.7.2.14-1.el6_6sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.3-1.el6_6sat.noarch qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-1.0-2.noarch foreman-vmware-1.7.2.14-1.el6_6sat.noarch ruby193-rubygem-foreman_discovery-2.0.0.9-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-1.7.2.14-1.el6_6sat.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el6_6sat.noarch ruby193-rubygem-foreman_docker-1.2.0.7-1.el6_6sat.noarch
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