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.
Log in to web UI, open "Add existing cluster" wizard.
1) When entering a node name and pressing enter, the node name is removed. Expected result: enter key triggers the "Check authentication" button.
2) When entering a node name and clicking the "Check authentication" button, a message "Node is authenticated. You can add the cluster now." is displayed. Pressing "Cancel" now closes the wizard. Click on "Add existing cluster" button opens the wizard in the same state. Expected result: Clicking "Cancel" purges data entered to the wizard.
DevTestResults:
[root@r91-1 ~]# rpm -q pcs
pcs-0.11.2-1.el9.x86_64
1. Log in to the Web UI and click on 'Add existing cluster' button.
2. In the 'Add existing cluster' wizard fill the 'Node name' field and hit 'Enter'
Result: Enter triggered the "Check authentication" button and wizard switched to the next step "Check node name"
3. Fill the password for the node and click "Authenticate"
Repeat action for other non-authenticated nodes until message "The cluster node is authenticated and it is possible to add the cluster to web ui."
4. click Cancel
5. click 'Add existing cluster'
Result: Wizard 'Add existing cluster' started without any previous data.
Only a basic check of the implemented modification of adding an existing cluster was performed.
If the 'cancel' button is used, the node name contained in the input is removed.
Our priority is to focus on automating these tasks in the future.
Marking as VERIFIED SanityOnly for pcs-0.11.3-3.el9
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 (Moderate: pcs security, 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/RHSA-2022:7935