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

Bug 1384696

Summary:	Node sends Ready Event before network is configured
Product:	OpenShift Container Platform	Reporter:	Eric Jones <erjones>
Component:	Networking	Assignee:	Dan Williams <dcbw>
Status:	CLOSED ERRATA	QA Contact:	Meng Bo <bmeng>
Severity:	medium	Docs Contact:
Priority:	high
Version:	3.3.0	CC:	aos-bugs, bbennett, hongli, jokerman, mmccomas, tdawson
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Previously nodes in an Openshift cluster using openshift-sdn would occasionally report readiness and be assigned pods before networking was fully configured. Nodes now only report readiness after networking is fully configured.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-18 12:42:44 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 Eric Jones 2016-10-13 21:49:10 UTC

Description of problem:
A node can send a Ready Event to the master (indicating it is prepared to receive pods) before the network is completely configured. In the specific instance that we found this issue the nodes did not have the networkConfig value set int he node-config.yaml but the nodes were seen as "Ready" even though they were not.

Version-Release number of selected component (if applicable):
OpenShift Container Platform 3.3

Comment 2 Ben Bennett 2016-10-26 19:52:04 UTC

Does this happen post-CNI?

Comment 3 Dan Williams 2016-10-27 15:52:43 UTC

This should no longer happen post-CNI, due to the new bits in the network plugin Status() hook that will return a periodic error to kubelet until the node has a HostSubnet assigned.

Comment 4 Troy Dawson 2016-11-02 17:52:05 UTC

What is post-CNI?
Or more important, is this fixed in OCP 3.3.1?  or OCP 3.4.0?  I'm trying to figure out which errata to attach it to.

Comment 5 Ben Bennett 2016-11-02 18:51:48 UTC

We changed the OpenShift networking plugin to use the CNI interface that changed quite a few of the internals for the better.

That happened in 3.4.  So it will not be fixed in 3.3.1.

Comment 6 Troy Dawson 2016-11-02 21:46:40 UTC

Thank you for the explanation.

Comment 8 Hongan Li 2016-11-03 10:29:13 UTC

verified on OCP 3.4.0.19 and con not reproduce the issue.

Will keep an eye on it since some CNI fixes have not been merged to this build.

Comment 10 errata-xmlrpc 2017-01-18 12:42:44 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, 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-2017:0066