Bug 1158491

Summary: 'pcs cluster status' is documented to be an alias to 'pcs status cluster' but has different output
Product: Red Hat Enterprise Linux 7 Reporter: Tomas Jelinek <tojeline>
Component: pcsAssignee: Tomas Jelinek <tojeline>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: low Docs Contact:
Priority: low    
Version: 7.1CC: cluster-maint, mlisik, rsteiger, tojeline
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pcs-0.9.140-1.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 09:32:59 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:

Description Tomas Jelinek 2014-10-29 13:49:58 UTC
Description of problem:
'pcs cluster status' command does not have the same output as the 'pcs status cluster' command but they are described as the same in man page and pcs help.

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

How reproducible:
always

Steps to Reproduce:
compare the output of 'pcs status cluster' and 'pcs cluster status' commands

Actual results:
[root@rh70-node1:~/devel/pcs/pcs]# diff <(./pcs status cluster) <(./pcs cluster status)
8a9,12
> 
> PCSD Status:
>   rh70-node1: Online
>   rh70-node2: Online

Expected results:
'pcs status cluster' and 'pcs cluster status' commands have the same output

Additional info:
github issue: https://github.com/feist/pcs/issues/35

Comment 3 Tomas Jelinek 2015-05-26 10:54:43 UTC
Fixed while working on bz1196412, fix is included in upstream patch:
https://github.com/feist/pcs/commit/8be3ac4314f6587efb5d0f25d665f6c9250ccee8

Test:
'pcs cluster status' has the same output as 'pcs status cluster'

Comment 5 Tomas Jelinek 2015-06-04 14:22:55 UTC
Before Fix:
[root@rh71-node1 ~]# rpm -q pcs
pcs-0.9.137-13.el7_1.2.x86_64
[root@rh71-node1:~]# diff <( pcs status cluster ) <( pcs cluster status )
8a9,13
> 
> PCSD Status:
>   rh71-node1: Online
>   rh71-node2: Online
>   rh71-node3: Online
[root@rh71-node1:~]# echo $?
1



After Fix:
[root@rh71-node1:~]# rpm -q pcs
pcs-0.9.140-1.el6.x86_64
[root@rh71-node1:~]# diff <( pcs status cluster ) <( pcs cluster status )
[root@rh71-node1:~]# echo $?
0

Comment 7 Miroslav Lisik 2015-07-03 18:09:07 UTC
Marking VERIFIED in pcs-0.9.141-1.el7.x86_64

BEFORE FIX:

[root@virt-012 ~]# rpm -q pcs
pcs-0.9.137-13.el7_1.3.x86_64

[root@virt-012 ~]# diff -u <(pcs status cluster) <(pcs cluster status)
--- /dev/fd/63  2015-07-03 19:33:22.520806579 +0200
+++ /dev/fd/62  2015-07-03 19:33:22.522806579 +0200
@@ -6,3 +6,8 @@
  Version: 1.1.12-a14efad
  3 Nodes configured
  9 Resources configured
+
+PCSD Status:
+  virt-012: Online
+  virt-013: Online
+  virt-014: Online

[root@virt-012 ~]# echo $?
1


AFTER FIX:

[root@virt-012 x86_64]# rpm -q pcs
pcs-0.9.141-1.el7.x86_64

[root@virt-012 x86_64]# diff -u <(pcs status cluster) <(pcs cluster status)
[root@virt-012 x86_64]# echo $?
0

Comment 9 errata-xmlrpc 2015-11-19 09:32:59 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/RHSA-2015-2290.html