Bug 1747841 - Restart kubelet service after etcd restore if node in NotReady status
Summary: Restart kubelet service after etcd restore if node in NotReady status
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 4.2.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Alay Patel
QA Contact: ge liu
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-02 03:20 UTC by ge liu
Modified: 2021-04-07 19:56 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-07 19:56:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.