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

Bug 1747841

Summary:	Restart kubelet service after etcd restore if node in NotReady status
Product:	OpenShift Container Platform	Reporter:	ge liu <geliu>
Component:	Documentation	Assignee:	Alay Patel <alpatel>
Status:	CLOSED CURRENTRELEASE	QA Contact:	ge liu <geliu>
Severity:	medium	Docs Contact:	Vikram Goyal <vigoyal>
Priority:	unspecified
Version:	4.2.0	CC:	ahoffer, aos-bugs, jokerman, kalexand
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-04-07 19:56:09 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 ge liu 2019-09-02 03:20:58 UTC

Description of problem:

As title, this issue is result from https://bugzilla.redhat.com/show_bug.cgi?id=1743190
as comments 8 mentioned, we need to  document the workaround(restart kubelet service) 

Alay Patel, could you help to draft the doc, then hand over to doc team? thanks in advance.

How reproducible:
Always

Steps to Reproduce:

Actual results:

Expected results

Comment 2 Andrea Hoffer 2021-04-07 19:56:09 UTC

Closing this BZ as we did indeed add the step to restart kubelet via https://github.com/openshift/openshift-docs/pull/23470 and https://bugzilla.redhat.com/show_bug.cgi?id=1850687.