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

Bug 1772097

Summary:	[DR] Recovery script fails to handle error during drain
Product:	OpenShift Container Platform	Reporter:	Suresh Kolichala <skolicha>
Component:	Etcd	Assignee:	Suresh Kolichala <skolicha>
Status:	CLOSED WONTFIX	QA Contact:	ge liu <geliu>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.2.z	CC:	geliu, mfojtik, sbatsche, skolicha
Target Milestone:	---
Target Release:	4.2.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1770273	Environment:
Last Closed:	2020-05-14 12:54:46 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:	1770273
Bug Blocks:

Description Suresh Kolichala 2019-11-13 15:57:40 UTC

+++ This bug was initially created as a clone of Bug #1770273 +++

Description of problem: crictl will return non 0 when using stop command if the container ID passed to it is not found. DR scripts do not gracefully handle this failure and should instead of exiting handle the error and retry until the drain is complete.

ref: https://coreos.slack.com/archives/C027U68LP/p1571942729031600

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results: DR completes as expected.


Additional info:

Comment 3 Michal Fojtik 2020-05-12 10:33:06 UTC

This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

As such, we're marking this bug as "LifecycleStale" and decreasing severity from "medium" to "low".

If you have further information on the current state of the bug, please update it, otherwise this bug will be automatically closed in 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

Comment 4 Suresh Kolichala 2020-05-14 12:54:46 UTC

We are not porting these fixes back to 4.2. Closing the BZ.