Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 2123326

Summary:	'pcs status' should show why resource is not running
Product:	Red Hat Enterprise Linux 9	Reporter:	michal novacek <mnovacek>
Component:	pcs	Assignee:	Tomas Jelinek <tojeline>
Status:	CLOSED MIGRATED	QA Contact:	cluster-qe <cluster-qe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	cluster-maint, idevat, mlisik, mpospisi, omular, phagara, tojeline
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-22 19:51:55 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 michal novacek 2022-09-01 12:14:20 UTC

Description of problem:

Currently, the only reason cluster gives for resource being at stopped state is when it is disable. No other reasons are marked when the resource is stopped.

This is making management of complex clusters with several tenths of resource and complex ordering constraints very uneasy and VERY user unfriendly when some of the resources are stopped when they should be running. 

Making users understand that easily from 'pcs setup' output would greatly improve their understanding of cluster and decrease the frustration level resulting in more love for HA.


Actual results:

When the resource is not running (shown Stopped) user must either show manually failcounts to see whether the resource is stopped because of the number of failures or if not go grep log files to see what is the real reason it stopped.


Expected results:

Show (or optionally dont) in pcs status why the resources is not running. Currently it would be great help to show at least:

  * "failcount" for when resource was tried to start but did fail
  * "blocked" for when the resource is not running due to ordering constraint to other resource

Comment 1 Patrik Hagara 2022-09-01 12:51:58 UTC

FWIW, there is a `crm_resource --why` pacemaker command which can detect and report the reason(s) why a resource is not running, in some very specific cases (target role == stopped, unmanaged, locked, stopped due to node health attribute [1]). This was added in bz#1298581.

AFAIK, it is not currently integrated into pcs' status output, but it sure would be nice!

[1] https://github.com/ClusterLabs/pacemaker/blob/344b73b73d1097464744ac75f471c77276df0394/tools/crm_resource_runtime.c#L972-L983

Comment 2 Tomas Jelinek 2022-09-05 13:34:15 UTC

If you really want this info to be present in 'pcs status' output, then it needs to be done in pacemaker.
If you are fine with adding a pcs command to expose the `crm_resource --why` functionality, then that can be done in pcs.
Let us know which variants are you asking for.

Thanks.

Comment 5 RHEL Program Management 2023-09-22 19:48:55 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 6 RHEL Program Management 2023-09-22 19:51:55 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.

Comment 7 Red Hat Bugzilla 2024-01-21 04:25:26 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days