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 1934651 - DB2: promote fails with HADR state PRIMARY/REMOTE_CATCHUP_PENDING/CONNECTED
Summary: DB2: promote fails with HADR state PRIMARY/REMOTE_CATCHUP_PENDING/CONNECTED
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: resource-agents
Version: 8.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Oyvind Albrigtsen
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 2127477
TreeView+ depends on / blocked
 
Reported: 2021-03-03 15:56 UTC by Ondrej Benes
Modified: 2024-06-14 00:37 UTC (History)
11 users (show)

Fixed In Version: resource-agents-4.1.1-93.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2127477 (view as bug list)
Environment:
Last Closed: 2021-11-09 17:26:02 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 6516791 0 None None None 2021-11-16 19:04:24 UTC
Red Hat Product Errata RHSA-2021:4139 0 None None None 2021-11-09 17:26:39 UTC

Comment 2 Reid Wahl 2021-03-03 19:52:12 UTC 
(In reply to Ondrej Benes from comment #0)
> Description of problem:
> promota action of the db2 resource agent fails with rc 1 if HADR state is
> PRIMARY/REMOTE_CATCHUP_PENDING/CONNECTED.
> 
> In bz1720283, state of STANDBY/REMOTE_CATCHUP_PENDING/DISCONNECTED was
> handled, but this is a different combination.

I wonder if this behavior is right or wrong. I'm not knowledgeable about DB2. But this article[1] says that remote catchup pending state happens when the connection between primary and secondary is lost while in remote catchup state or when it has not yet been established.

[1] https://www.ibm.com/support/knowledgecenter/en/SSEPGG_11.5.0/com.ibm.db2.luw.admin.ha.doc/doc/c0011748.html


I haven't been able to find any information about when HADR_ROLE=PRIMARY and HADR_STATE=REMOTE_CATCHUP_PENDING. I can only find HADR_STATE=REMOTE_CATCHUP_PENDING when HADR_ROLE=STANDBY.

So I wonder whether the state described here (PRIMARY/REMOTE_CATCHUP_PENDING) is actually healthy enough to promote the instance or not. Initiating a "by force" takeover wouldn't make sense, since we're already in the primary role. We just don't have a connection to the standby.

Perhaps it would be fine to go ahead and promote, since this status essentially means "we're primary but we lost or haven't established connection with the standby" -- which seems realistic in an HA scenario.


Will wait for further thoughts from Oyvind or IBM.
Comment 6 Oyvind Albrigtsen 2021-04-12 10:53:57 UTC 
Tested patch: https://github.com/ClusterLabs/resource-agents/pull/1634
Comment 9 Dean Jansa 2021-04-14 09:00:54 UTC 
ON_QA bug without Verified:Tested should be in the MODIFIED state.
Comment 11 Dean Jansa 2021-04-15 08:00:59 UTC 
ON_QA bug without Verified:Tested should be in the MODIFIED state.
Comment 17 errata-xmlrpc 2021-11-09 17:26:02 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 (Moderate: resource-agents security, 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/RHSA-2021:4139
Note You need to log in before you can comment on or make changes to this bug.