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 1158491 - 'pcs cluster status' is documented to be an alias to 'pcs status cluster' but has different output
Summary: 'pcs cluster status' is documented to be an alias to 'pcs status cluster' but...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pcs
Version: 7.1
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Tomas Jelinek
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-29 13:49 UTC by Tomas Jelinek
Modified: 2015-11-19 09:32 UTC (History)
4 users (show)

Fixed In Version: pcs-0.9.140-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 09:32:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1188659 0 medium CLOSED pcsd status detection is slow 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1207405 0 medium CLOSED RFE: please adjust timeouts for pcsd check (or allow to disable them) 2021-10-05 17:55:02 UTC
Red Hat Product Errata RHSA-2015:2290 0 normal SHIPPED_LIVE Moderate: pcs security, bug fix, and enhancement update 2015-11-19 09:43:53 UTC

Internal Links: 1188659 1207405

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
Note You need to log in before you can comment on or make changes to this bug.