Bug 1243744

Summary: Fix default transport in pcs help and man page
Product: Red Hat Enterprise Linux 6 Reporter: Tomas Jelinek <tojeline>
Component: pcsAssignee: Tomas Jelinek <tojeline>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 6.7CC: cluster-maint, fdanapfe, rsteiger, tojeline
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pcs-0.9.145-1.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-10 19:27:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
proposed fix none

Description Tomas Jelinek 2015-07-16 08:26:07 UTC 
Both "pcs cluster help" and "man pcs" incorrectly state that udpu is the default transport on RHEL6:

# rpm -q pcs
pcs-0.9.123-9.el6_6.2.x86_64
# pcs cluster help

Usage: pcs cluster [commands]...
...


--transport allows specification of corosync transport (default: udpu)
...
Configuring Redundant Ring Protocol (RRP)

When using udpu (the default) specifying nodes, specify the ring 0
...

Maybe this can be corrected.



Thanks to Frank Danapfel for pointing this out.
We should also take a look at the new cluster dialog in web UI.
Comment 1 Tomas Jelinek 2015-09-18 13:06:26 UTC 
Created attachment 1074901 [details]
proposed fix

help and man page changes only
Comment 2 Tomas Jelinek 2015-11-04 11:38:06 UTC 
Before Fix:
[root@rh67-node1 ~]# rpm -q pcs
pcs-0.9.139-9.el6_7.1.x86_64
Run "pcs cluster help setup". It is stated that udpu is the default transport.



After Fix:
[root@rh67-node1:~]# rpm -q pcs
pcs-0.9.145-1.el6.x86_64
Run "pcs cluster help setup". It is stated that udp is the default transport on RHEL 6.
Comment 6 errata-xmlrpc 2016-05-10 19:27:54 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-2016-0739.html