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

Bug 1768252

Summary:	node failed to become ready
Product:	OpenShift Container Platform	Reporter:	Ben Parees <bparees>
Component:	Etcd	Assignee:	Sam Batschelet <sbatsche>
Status:	CLOSED NOTABUG	QA Contact:	ge liu <geliu>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.3.0	CC:	aos-bugs, jerzhang, jokerman, lszaszki, mfojtik, rphillips, sttts
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-02-25 10:26:45 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 Ben Parees 2019-11-03 17:38:57 UTC

Description of problem:
Azure CI job failure appears to be due to issues w/ nodes coming online:

level=error msg="Cluster operator kube-apiserver Degraded is True with MultipleConditionsMatching: NodeControllerDegraded: The master node(s) \"ci-op-c2szz6wi-09f59-79jcb-master-2\" not ready\nNodeInstallerDegraded: 1 nodes are failing on revision 2:\nNodeInstallerDegraded: static pod of revision has been installed, but is not ready while new revision 2 is pending\nStaticPodsDegraded: nodes/ci-op-c2szz6wi-09f59-79jcb-master-2 pods/kube-apiserver-ci-op-c2szz6wi-09f59-79jcb-master-2 container=\"kube-apiserver-3\" is not ready\nStaticPodsDegraded: nodes/ci-op-c2szz6wi-09f59-79jcb-master-2 pods/kube-apiserver-ci-op-c2szz6wi-09f59-79jcb-master-2 container=\"kube-apiserver-3\" is waiting: \"CreateContainerError\" - \"error reserving ctr name k8s_kube-apiserver-3_kube-apiserver-ci-op-c2szz6wi-09f59-79jcb-master-2_openshift-kube-apiserver_4088b848fe9d576c87c07c1cab17e65e_3 for id 124eeb8c1cef2c328eaa88eed15a988a54b760b5d1c41aff65206738907ec038\""
level=info msg="Cluster operator kube-apiserver Progressing is True with Progressing: Progressing: 2 nodes are at revision 0; 1 nodes are at revision 2; 0 nodes have achieved new revision 3"

job:
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-azure-serial-4.3/306

Comment 6 Michal Fojtik 2020-02-25 10:26:45 UTC

Closing this bug as this was expected Azure behavior.