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 1072415 - pcs GUI should support creating dual-ring clusters (RRP)
Summary: pcs GUI should support creating dual-ring clusters (RRP)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pcs
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Tomas Jelinek
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks: 1129867
TreeView+ depends on / blocked
 
Reported: 2014-03-04 14:35 UTC by Radek Steiger
Modified: 2015-03-05 09:19 UTC (History)
7 users (show)

Fixed In Version: pcs-0.9.130-1.el7
Doc Type: Bug Fix
Doc Text:
Cause: User tries to create a cluster with Redundant Ring Protocol (RRP) using pcsd GUI. Consequence: GUI provides no way to create a cluster with RRP. Fix: Add RRP options to the 'Create cluster' dialog and 'Add node' dialog. Result: User is able to create a cluster with RRP and add / remove nodes using pcsd GUI.
Clone Of: 915894
: 1129867 (view as bug list)
Environment:
Last Closed: 2015-03-05 09:19:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
proposed fix 1/2 (12.90 KB, patch)
2014-09-09 13:10 UTC, Tomas Jelinek
no flags Details | Diff
proposed fix 2/2 (15.56 KB, patch)
2014-09-09 13:10 UTC, Tomas Jelinek
no flags Details | Diff
proposed fix 3 - defaults in Create Cluster dialog (9.40 KB, patch)
2014-09-24 11:31 UTC, Tomas Jelinek
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0415 0 normal SHIPPED_LIVE pcs bug fix and enhancement update 2015-03-05 14:16:41 UTC

Comment 3 Tomas Jelinek 2014-09-09 13:10:03 UTC
Created attachment 935688 [details]
proposed fix 1/2

Comment 4 Tomas Jelinek 2014-09-09 13:10:27 UTC
Created attachment 935689 [details]
proposed fix 2/2

Comment 5 Tomas Jelinek 2014-09-09 13:12:14 UTC
test

A. RRP with udpu transport
1. Open the 'Create Cluster' dialog. Specify 'Cluster Name' and nodes. Show 'Advanced Options'. Select 'Transport' = 'UDPU'. Verify that the dialog provides fields for ring 1 addresses. Fill in the ring 1 addresses. Submit the form.
2. Show the created cluster in GUI verifying the cluster has been created.
3. Add a node to the cluster using GUI. Verify that the dialog provides a field for the ring 1 address. Specify the ring 1 address when adding the node.
4. Using GUI verify that the node has been added to the cluster.
5. Connect to any node of the cluster using ssh. Display the /etc/corosync/corosync.conf file. Verify there are ring 1 addresses for the nodes as were specified in the dialogs.

B. RRP with udp transport
1. Open the 'Create Cluster' dialog. Specify 'Cluster Name' and nodes. Show 'Advanced Options'. Select 'Transport' = 'UDP'. Verify that the dialog provides fields for ring 0 and ring 1 settings. Fill in the ring 0 and ring 1 settings. Submit the form.
2. Show the created cluster in GUI verifying the cluster has been created.
3. Add a node to the cluster using GUI. Verify that there is no field for a ring 1 address in the dialog.
4. Using GUI verify that the node has been added to the cluster.
5. Connect to any node of the cluster using ssh. Display the /etc/corosync/corosync.conf file. Verify there are ring 0 and ring 1 settings as were specified in the dialogs.

Comment 6 Tomas Jelinek 2014-09-15 08:45:48 UTC
Before Fix:
[root@rh70-node1 ~]# rpm -q pcs
pcs-0.9.115-32.el7.x86_64

Open 'Create Cluster' dialog in GUI. No RRP options available.


After Fix:
[root@rh70-node1 ~]# rpm -q pcs
pcs-0.9.127-1.el7.x86_64

Open 'Create Cluster' dialog in GUI. RRP options are available for both UDPU and UDP transport in 'Advanced Options' part of the dialog.

Comment 8 Tomas Jelinek 2014-09-24 11:31:32 UTC
Created attachment 940740 [details]
proposed fix 3 - defaults in Create Cluster dialog

Comment 9 Tomas Jelinek 2014-09-26 14:45:43 UTC
Before Fix:
[root@rh70-node1 ~]# rpm -q pcs
pcs-0.9.127-1.el7.x86_64

Navigate to the "Manage Clusters" page in GUI. Open the "Create Cluster" dialog, open "Advanced Options". Inputs (token settings, last man standing, RRP settings) are pre-filled with default values. Fill in the cluster name and nodes and create the cluster. Default values from the inputs have been saved into /etc/corosync/corosync.conf file.


After Fix:
[root@rh70-node1:~]# rpm -q pcs
pcs-0.9.130-1.el7.x86_64

Navigate to the "Manage Clusters" page in GUI. Open the "Create Cluster" dialog, open "Advanced Options". Inputs are not pre-filled with default values. Fill in the cluster name and nodes and create the cluster. The /etc/corosync/corosync.conf file does not contain values of token settings, last man standing, RRP settings unless they were specified in the dialog.

Comment 13 errata-xmlrpc 2015-03-05 09:19:03 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, 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-0415.html


Note You need to log in before you can comment on or make changes to this bug.