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 1486869 - RFE: crm_mon deal with inactive cluster better
Summary: RFE: crm_mon deal with inactive cluster better
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pacemaker
Version: 7.6
Hardware: x86_64
OS: Linux
low
low
Target Milestone: rc
: 7.7
Assignee: Ken Gaillot
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-30 16:24 UTC by Corey Marthaler
Modified: 2020-12-11 16:52 UTC (History)
8 users (show)

Fixed In Version: pacemaker-1.1.20-1.el7
Doc Type: No Doc Update
Doc Text:
Minor self-explanatory enhancement
Clone Of:
Environment:
Last Closed: 2019-08-06 12:53:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2129 0 None None None 2019-08-06 12:54:08 UTC

Internal Links: 1728704

Description Corey Marthaler 2017-08-30 16:24:02 UTC 
Description of problem:

[root@host-113 ~]# pcs status
Error: cluster is not currently running on this node

[root@host-113 ~]# crm_mon
Attempting connection to the cluster...
[stuck]

[root@host-113 ~]# crm_mon -X
Connection to cluster failed: Transport endpoint is not connected

Both the above two cmds should warn like the first one did.
 

Version-Release number of selected component (if applicable):
pacemaker-cli-1.1.16-12.el7.x86_64
pacemaker-doc-1.1.16-12.el7.x86_64
pacemaker-libs-1.1.16-12.el7.x86_64
pacemaker-cluster-libs-1.1.16-12.el7.x86_64
pacemaker-1.1.16-12.el7.x86_64
Comment 3 Ken Gaillot 2017-08-30 16:55:04 UTC 
"crm_mon" runs in interactive mode, which shouldn't exit until the user tells it to, but we could improve the message -- maybe "Waiting until cluster is available on this node ...".

For "crm_mon -X", I'm thinking "Error: cluster is not available on this node". pcs might have some more intelligence like checking for cluster processes, but all crm_mon knows is that it couldn't connect. The most likely reason is that the cluster is not running, but it could be something else, like our connection being blocked somehow. I think "not available" covers all the bases.

Let me know if you have a better suggestion.
Comment 4 Corey Marthaler 2017-08-30 19:29:16 UTC 
both above suggestions sound fine. Thanks.
Comment 7 Ken Gaillot 2018-12-18 21:11:04 UTC 
Moving to RHEL 8 only, as this will not make 7.7, which will be the last RHEL 7 feature release
Comment 8 Klaus Wenninger 2018-12-19 12:26:20 UTC 
Hasn't that been taken care of upstream already both on the master as the 1.0 branch?
Guess it is already in 8.0 and should get into 7.7 via rebase.

pacemaker-2.0:
commit 3795ed48e40141fd72d869be05a03a758450dd68
Author: Klaus Wenninger <klaus.wenninger>
Date:   Mon Aug 20 14:02:41 2018 +0200

    Fix: crm_mon: rhbz#1486869 - common language on connection-errors
    
    make a cluster-connection-failure CRIT instead of WARN for nagios


pacemaker-1.1:
commit 7d9806020a17556272a1ab7ee8eb4d4228ea8667
Author: Klaus Wenninger <klaus.wenninger>
Date:   Mon Aug 20 14:02:41 2018 +0200

    Fix: crm_mon: rhbz#1486869 - common language on connection-errors
    
    make a cluster-connection-failure CRIT instead of WARN for nagios

Sorry seems as if I missed to put that in here.
Comment 10 Ken Gaillot 2018-12-19 15:33:56 UTC 
QA: Trivial verification, run crm_mon when no cluster is running:

% crm_mon -1

Error: cluster is not available on this node

% crm_mon -X

Error: cluster is not available on this node

% crm_mon

Waiting until cluster is available on this node ...
Comment 13 Patrik Hagara 2019-07-01 10:55:24 UTC 
before (1.1.19-8.el7):
======================

> [root@virt-130 ~]# rpm -q pacemaker
> pacemaker-1.1.19-8.el7.x86_64
> [root@virt-130 ~]# pcs status      
> Error: cluster is not currently running on this node
> [root@virt-130 ~]# crm_mon -1
> 
> Connection to cluster failed: Transport endpoint is not connected
> [root@virt-130 ~]# crm_mon -X
> 
> Connection to cluster failed: Transport endpoint is not connected
> [root@virt-130 ~]# crm_mon
> Attempting connection to the cluster...
> [stuck]

result: failure message unclear (connection error).


after (1.1.20-5.el7):
=====================

> [root@virt-054 ~]# rpm -q pacemaker
> pacemaker-1.1.20-5.el7.x86_64
> [root@virt-054 ~]# pcs status
> Error: cluster is not currently running on this node
> [root@virt-054 ~]# crm_mon -1
> 
> Error: cluster is not available on this node
> [root@virt-054 ~]# crm_mon -X
> 
> Error: cluster is not available on this node
> [root@virt-054 ~]# crm_mon
> Waiting until cluster is available on this node ...
> [stuck]

result: better failure message (cluster not available).


Marking as verified in 1.1.20-5.el7.
Comment 15 errata-xmlrpc 2019-08-06 12:53:38 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://access.redhat.com/errata/RHBA-2019:2129
Note You need to log in before you can comment on or make changes to this bug.