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.
Cause:
WebUI code contained error that didn't allow to setup cluster without an explicit specification of knet links.
Consequence:
A user could not setup cluster without an explicit specification of knet links.
Fix:
The error in webUI was fixed.
Result:
A user can setup cluster without an explicit specification of knet links.
Created attachment 1542983[details]
pcsd_virt-151.log
Description of problem:
Cannot create cluster with pcs GUI.
Version-Release number of selected component (if applicable):
pcs-0.10.1-4.el8
How reproducible:
always
Steps to Reproduce:
1. setup password for hacluster user on the host for cluster nodes
# echo password | passwd hacluster --stdin
2. Enable and start pcsd daemon
# systemctl enable pcsd
# systemctl start pcsd
3. Go to pcs GUI address: https:/<hostname>:2224/
e.g.
https://virt-151.cluster-qe.lab.eng.brq.redhat.com:2224/
4. Log in as hacluster using your password
5. On manage page click on "Create New"
6. "Create cluster" dialog pops up and fill the "Cluster name", "Node 1" and Node2" fields.
e.g.
Cluster Name: TestCluster
Node1: virt-151.cluster-qe.lab.eng.brq.redhat.com
Node2: virt-152.cluster-qe.lab.eng.brq.redhat.com
7. Click on "Create cluster" button and "Authentification of nodes" dialog pops up.
8. Check checkbox "Use same password for all nodes" and fill the password.
9. Click on "Authenticate" button.
10. "Authentication of nodes" dialog disappears and "Create cluster" dialog is still visible but "Create cluster" and "Go to advance settings" buttons are inactive.
11. Check the corosync.conf file on the nodes
# ls /etc/corosync/corosync.conf
ls: cannot access '/etc/corosync/corosync.conf': No such file or directory
Actual results:
Cluster is not created. Corosync file is not even created on the nodes.
Expected results:
Cluster is created.
Additional info:
Pcsd debug logs are attached.
There is error message in browser console:
api.js:216 Uncaught TypeError: Cannot read property 'filter' of undefined
at api.js:216
at Array.map (<anonymous>)
at Object.api.clusterSetup (api.js:214)
at Object.<anonymous> (cluster-setup.js:711)
at Object.<anonymous> (jquery-1.9.1.min.js:3)
at c (jquery-1.9.1.min.js:3)
at Object.fireWith [as resolveWith] (jquery-1.9.1.min.js:3)
at Object.i.(anonymous function) (https://virt-151.cluster-qe.lab.eng.brq.redhat.com:2224/js/jquery-1.9.1.min.js:3:9642)
at c (jquery-1.9.1.min.js:3)
at Object.add [as done] (jquery-1.9.1.min.js:3)
Workarounds:
A) create a cluster in GUI
* in step 7, click "Go to advance settings" instead of "Create cluster"
* once you go through nodes authentication and get to advanced setup dialog, click "Add link..."
* click "Create cluster", no need to actually fill-in anything in the form
B) create a cluster in CLI
After fix:
[root@rhel81-node1 ~]# rpm -q pcs
pcs-0.10.1-6.el8.x86_64
> It is possible to create a cluster using web UI following steps described in comment 0
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/RHEA-2019:3311