Bug 1321828

Summary:	[RFE] Should avoid openshift node to be started if it configured as different network plugin with master
Product:	OKD	Reporter:	Meng Bo <bmeng>
Component:	Networking	Assignee:	Ravi Sankar <rpenta>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Meng Bo <bmeng>
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.x	CC:	aos-bugs, rpenta, zzhao
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-19 13:49:35 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:

Description Meng Bo 2016-03-29 08:47:57 UTC

Description of problem:
For now, if configured different network plugins for master and node, both the services will run well. But the created pods will be in mal-function.

If master is configured as multi-tenant, and nodes are configured as subnet, the pods created on nodes will use the flat network.

If master is configured as subnet and nodes are configured as multi-tenant, the pods will not be created due to error fetching VNID.

It is better to avoid these kinds of conditions before the services are running.



Version-Release number of selected component (if applicable):
openshift v1.1.4-314-ge2e226f

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:
Node service can be ran if the network plugin has different configuration with master.

Expected results:
Should not start the node service if the network plugin does not match master config.

Additional info:

Comment 1 Ravi Sankar 2016-06-17 00:36:56 UTC

Fixed in https://github.com/openshift/origin/pull/9147

Comment 2 zhaozhanqi 2016-06-22 01:37:37 UTC

verified this bug with version:

openshift version
openshift v1.3.0-alpha.1-406-gda4eb9c
kubernetes v1.3.0-alpha.3-599-g2746284
etcd 2.3.0+git