Red Hat Bugzilla – Bug 1465133
Invalid network plugin name does not cause master process fail
Last modified: 2017-06-26 20:20:22 EDT
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):
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
Master process restart does not fail
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).