Bug 1944394

Summary: Wrong Openshift node IP as kubelet setting VIP as node IP
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: NetworkingAssignee: Dan Winship <danw>
Networking sub component: openshift-sdn QA Contact: zhaozhanqi <zzhao>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: unspecified CC: aconstan, akaris, bbennett, ctauchen, danw, openshift-bugs-escalate, rcarrier, trozet, wking
Version: 4.7   
Target Milestone: ---   
Target Release: 4.7.z   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: kubelet picks wrong node IP, in unclear circumstances Consequence: Node becomes NotReady immediately after boot, until it is rebooted Fix: kubelet should reliably use the correct node IP Result: no NotReady nodes
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-04-20 18:52:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1940939    
Bug Blocks:    

Comment 3 zhaozhanqi 2021-04-12 12:18:44 UTC
Verified this bug on 4.7.0-0.nightly-2021-04-10-082109


[kni@provisionhost-0-0 ~]$ oc debug node/master-0-0 --image='quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:d7fdcdcc2754359ab49422d6f2f3e9612eb4332ed73d58705c5f086c343d3793'
Starting pod/master-0-0-debug ...
To use host binaries, run `chroot /host`
Pod IP: 192.168.123.109
If you don't see a command prompt, try pressing enter.
sh-4.4# chroot /host
sh-4.4# systemctl show --property=NeedDaemonReload kubelet
NeedDaemonReload=no

Comment 7 errata-xmlrpc 2021-04-20 18:52:39 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 (OpenShift Container Platform 4.7.7 bug fix 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-2021:1149

Comment 8 Dan Winship 2021-07-15 14:35:31 UTC
*** Bug 1922812 has been marked as a duplicate of this bug. ***