Description of problem: Making network plugin name invalid in master-config and restarting master process, master process start does not fail. Version-Release number of selected component (if applicable): openshift v3.6.116 kubernetes v1.6.1+5115d708d7 etcd 3.2.0 How reproducible: always Steps to Reproduce: 1. create a cluster with valid network plugin 2. modify network plugin in master-config to invalid value 3. restart master process Actual results: Master process restart does not fail Expected results: Master process start should fail.
A network plugin with an invalid name does cause the atomic-openshift-node process to fail on startup.
Since people can install arbitrary network plugins, we can't know it is invalid until the node attempts to run it. The master doesn't use a network plugin (but we recommend that the master machine also have a node setup on it so the machine is part of the SDN).