Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
> Description of problem:
ID attribute of HTML elements that represent each resource in the GUI resource list is generated dynamically according to the resource name, but instead of using a deterministic pre/post-fix or a completely random and therefore unique ID it only takes the corresponding resource's name and uses it as an ID. This enables the user to create such a resource which name used as an ID would collide with some other ID that already exists inside the GUI page, possibly causing an unexpected behavior.
The most simple reproducer is to create a resource called 'test'. As the ID 'test' is already reserved by parts of the javascript framework the result of this particular case is making the resource non-highlightable within the resource list.
Another one is to use browser's developer tools and xpath to search for particular ID, i.e. run $x("//*[@id='test']") in Chrome's console to verify that ID is present more than once.
> Version-Release number of selected component (if applicable):
pcs-0.9.152-6.el7.x86_64
> Steps to Reproduce:
1. Create a resource called 'test'
2. Try to highlight the resource inside resource list
> Actual results:
Item cannot be highlighted. Also, an xpath search would return more than one instance of the correspondent ID.
> Expected results:
Item can be highlighted. Also, an xpath search would return just one instance of the correspondent ID.
Setup:
Create resource called 'test'.
Before Fix:
[vm-rhel72-1 ~] $ rpm -q pcs
pcs-0.9.152-6.el7.x86_64
In web UI select resource 'test'. It is not highlighted.
After Fix:
[vm-rhel72-1 ~] $ rpm -q pcs
pcs-0.9.152-7.el7.x86_64
In web UI select resource 'test'. It is highlighted.
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/RHSA-2016-2596.html