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 2118745

Summary:	SAPInstance cluster resources not getting enabled after implementing sap-cluster-connector [rhel-8.6.0.z]
Product:	Red Hat Enterprise Linux 8	Reporter:	RHEL Program Management Team <pgm-rhel-tools>
Component:	pacemaker	Assignee:	Ken Gaillot <kgaillot>
Status:	CLOSED ERRATA	QA Contact:	cluster-qe <cluster-qe>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	8.6	CC:	amemon, cfeist, cluster-maint, cluster-qe, fdanapfe, hbiswas, jfuchs, jserrano, mjuricek, mmoster, msmazova, oalbrigt, sbradley
Target Milestone:	rc	Keywords:	Regression, Triaged, ZStream
Target Release:	8.6	Flags:	pm-rhel: mirror+
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	pacemaker-2.1.2-4.el8_6.3	Doc Type:	Bug Fix
Doc Text:	Cause: The Pacemaker versions in RHEL 8.5 and 9.0 beta and later, for the crm_resource -O command to list operations, use a minimum of 0 for execution status. Consequence: A pending command, which has an execution status of -1, is shown as complete (0). Fix: crm_resource -O now uses a minimum of -1 for execution status. Result: Pending commands are appropriately shown as pending.	Story Points:	---
Clone Of:	2118337	Environment:
Last Closed:	2022-09-13 09:48:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2118337
Bug Blocks:

Comment 1 Ken Gaillot 2022-08-16 19:04:51 UTC

Fixed in upstream main branch by commit fe9150bc

Comment 2 Ken Gaillot 2022-08-17 19:33:48 UTC

QA: Reproducer is same as for parent bz:

    CIB_file=/usr/share/pacemaker/tests/scheduler/xml/probe-1.xml crm_resource -O

Before:

    DcIPaddr        (ocf::heartbeat:IPaddr):         Stopped: DcIPaddr_monitor_0 (node=c001n05, call=2, rc=-1): complete

After:

    DcIPaddr        (ocf::heartbeat:IPaddr):         Stopped: DcIPaddr_monitor_0 (node=c001n05, call=2, rc=-1): pending

"crm_resource -O" in a live cluster with a pending operation would also show the issue.

Comment 12 errata-xmlrpc 2022-09-13 09:48:19 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 (pacemaker bug fix and enhancement update), 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-2022:6451