Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1880451 - Node becoming NotReady frequently with openshift IPI on vsphere [NEEDINFO]
Summary: Node becoming NotReady frequently with openshift IPI on vsphere
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Machine Config Operator
Version: 4.5
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.9.0
Assignee: Ben Nemec
QA Contact: Michael Nguyen
Depends On:
TreeView+ depends on / blocked
Reported: 2020-09-18 15:19 UTC by puraut
Modified: 2021-07-07 00:32 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:
sttts: needinfo? (puraut)

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 5438831 0 None None None 2020-09-28 09:30:14 UTC

Description puraut 2020-09-18 15:19:07 UTC
Description of problem:
RHOCP 4.5 node become not ready and freqently 

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

How reproducible:
Every time on vsphere 

Steps to Reproduce:
1.Install 4.5.8 cluster and let it run for > 24hrs 

Actual results:
1]Node not ready :kubelet unable to post status though it is runing 
2] unable to reslove api-int with ipi installtion: 
nslookup  api-int.ocp46aipi.ocp.gsslab.pnq2.redhat.com
;; Got recursion not available from, trying next server                   <----------- trying to first reslover not working
Server:                                                             <----------  it went for outside cluster 

** server can't find api-int.ocp46aipi.ocp.gsslab.pnq2.redhat.com: NXDOMAIN

nslookup sucess 

nslookup -debug api-int.ocp46aipi.ocp.gsslab.pnq2.redhat.com
Server:         <-- node IP

Name:	api-int.ocp46aipi.ocp.gsslab.pnq2.redhat.com

Expected results:
Cluster should be up and running 

Additional info:

Attaching sosreport of node and cluster details

Comment 3 Andrew McDermott 2020-09-21 17:18:44 UTC
Target set to next release version while investigation is either ongoing or pending. Will be considered for earlier release versions when diagnosed and resolved.

Note You need to log in before you can comment on or make changes to this bug.