Bug 1465133 - Invalid network plugin name does not cause master process fail
Summary: Invalid network plugin name does not cause master process fail
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Ben Bennett
QA Contact: Meng Bo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-26 17:57 UTC by Vikas Laad
Modified: 2017-06-27 00:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-27 00:20:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Vikas Laad 2017-06-26 17:57:02 UTC
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.

Comment 1 Mike Fiedler 2017-06-26 21:50:30 UTC
A network plugin with an invalid name does cause the atomic-openshift-node process to fail on startup.

Comment 2 Ben Bennett 2017-06-27 00:20:10 UTC
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).


Note You need to log in before you can comment on or make changes to this bug.