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.
Bug 2167471 - [WebUI] Broken typeahead component
Summary: [WebUI] Broken typeahead component
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: pcs
Version: 9.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 9.2
Assignee: Michal Pospisil
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-06 17:42 UTC by Michal Pospisil
Modified: 2023-05-09 07:40 UTC (History)
9 users (show)

Fixed In Version: pcs-0.11.4-6.el9
Doc Type: No Doc Update
Doc Text:
Affected packages have not been released.
Clone Of:
Environment:
Last Closed: 2023-05-09 07:18:58 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CLUSTERQE-6405 0 None None None 2023-02-07 12:06:37 UTC
Red Hat Issue Tracker RHELPLAN-147664 0 None None None 2023-02-06 17:43:36 UTC
Red Hat Product Errata RHBA-2023:2151 0 None None None 2023-05-09 07:19:05 UTC

Description Michal Pospisil 2023-02-06 17:42:27 UTC 
Description of problem:
Typeahead components are unusable for filtering dropdowns in create resource or create fence device wizards.

Version-Release number of selected component (if applicable):
pcs-0.11.4-1

How reproducible:
always, easily

Steps to Reproduce:
1. Go to cluster detail.
2. Open `Fence Devices`/`Resources` tab. 
3. Click on the `Create Fence Device`/`Create Resource` button.
4. Click on the `Fence device type`/`Create Resource` typeahead component - it's a searchable dropdown.

Actual results:
5. A list of selectable options appears, text cursor briefly appears and vanishes quickly. Typing in the typeahead is not possible. 
6. Click on the typeahead again, the cursor starts flashing, typing is now possible.
7. Start writing - only one character is accepted and the list is updated. The cursor vanishes right away, no further input is recognized.
8. Click on the typeahaed to continue writing. The lone character in the typeahead is erased and previously displayed list vanishes. Search is therefore unusable.

Expected results:
5. Cursor is flashing and typing in the typeahead is possible.
6. ---
7. It is possible to type and erase characters in the typeahead and list updates after every written/erased character.
8. Clicking into the typeahead doesn't erase characters, only the cursor location changes.

Additional info:
Comment 3 Michal Pospisil 2023-02-13 15:21:35 UTC 
Upstream patch: https://github.com/ClusterLabs/pcs-web-ui/commit/10bb303b4c26602da6d3be0a2389930b2ca9c6c8
Comment 4 Michal Pospisil 2023-02-14 09:29:43 UTC 
DevTestResults:

[root@r09-02-a ~]# rpm -q pcs
pcs-0.11.4-6.el9.x86_64

The behavior of the typeahead component was checked in create resource and create fence device wizards respectively. The component now works as described in expected results in comment 0.
Comment 8 svalasti 2023-02-20 11:57:47 UTC 
[root@virt-508 ~]# rpm -q pcs
pcs-0.11.4-4.el9.x86_64

Only a basic check of this implemented feature has been performed. Our priority at the moment is to automate the tasks that are possible by using the GUI.

Steps to Reproduce:

## Find dropdown component:
    1. Go to cluster detail.
    2. Open `Fence Devices`/`Resources` tab. 
    3. Click on the `Create Fence Device`/`Create Resource` button.
    4. Click on the `Fence device type`/`Create Resource` typeahead component - it's a searchable dropdown.
> The points described above also work correctly for the current version. After adding an existing cluster or performing a cluster setup, the functionality is unchanged.

## Searching for desired resource type or fence device type (+ filtering):
    5. Cursor is flashing and typing in the typeahead is possible.
    6. ---
    7. It is possible to type and erase characters in the typeahead and list updates after every written/erased character.
    8. Clicking into the typeahead doesn't erase characters, only the cursor location changes.
> Clicking on the typehead component makes it possible to type or erase characters. Users can search for the desired fence device or resource type. The filtering of the search in this dropdown works reliably.


> Marking as VERIFIED SanityOnly for pcs-0.11.4-4.el9
Comment 10 errata-xmlrpc 2023-05-09 07:18:58 UTC 
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 (pcs bug fix and enhancement update), 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/RHBA-2023:2151
Note You need to log in before you can comment on or make changes to this bug.