Description of problem: After creating an alert profile, if I try to edit its assignments, I get the following behavior: I select "Tagged Hosts / Nodes", pick a tag category, and see a list of checkboxes appear. However, I am unable to check any checkbox. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create an alert profile 2. "Edit assignements for this alert profile" 3. Try to select a checkbox Actual results: No checkboxes are checked Expected results: Checkboxes are checked Additional info: This issue happened in a web instance where only an openstack infrastructure provider was registered, resulting in a change in UI labels; not sure if this has the potential to cause this error.
New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/15d6e2c60671d5136432bed4bc547e0a254c64b7 commit 15d6e2c60671d5136432bed4bc547e0a254c64b7 Author: Harpreet Kataria <hkataria> AuthorDate: Wed May 6 16:38:44 2015 -0400 Commit: Harpreet Kataria <hkataria> CommitDate: Wed May 6 16:38:44 2015 -0400 Renamed a JS function that can be called/used from multiple screens. - Renamed existing method 'cfmeOnClick_RoleFeatureCheck' method to 'miqOnCheck_handler' so it can be called/used from other places as well. This issue was caused by removal of 'cfmeOnClick_SmartProxyAffinityCheck' JS function in https://github.com/ManageIQ/manageiq/pull/1531 that was identical to 'cfmeOnClick_RoleFeatureCheck' function. - Fixed an issue with sort that was causing the screen to blow up after Alert Profile assignment was saved https://bugzilla.redhat.com/show_bug.cgi?id=1219171 vmdb/app/assets/javascripts/miq_dynatree.js | 10 +++------- vmdb/app/views/miq_policy/_alert_profile_assign.html.haml | 2 +- vmdb/app/views/miq_policy/_alert_profile_details.html.haml | 2 +- vmdb/app/views/ops/_rbac_role_details.html.haml | 2 +- 4 files changed, 6 insertions(+), 10 deletions(-)
Verified in 5.4.0.0.26
*** Bug 1221361 has been marked as a duplicate of this bug. ***
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://rhn.redhat.com/errata/RHBA-2015-1100.html