Hide Forgot
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:
Fixed in https://github.com/openshift/origin/pull/9147
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