Description of problem: Node service stays on "Activating" when --disable=proxy is added in the /etc/sysconfig/atomic-openshift-node file. This is performed as requirement for third party network plugin integration, as explained in https://github.com/openshift/origin/blob/master/docs/openshift_networking_requirements.md#advanced-requirements Error: atomic-openshift-node[26524]: E0807 04:45:54.161756 26524 runtime.go:66] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference) Version-Release number of selected component (if applicable): # oc version oc v3.5.5.31 kubernetes v1.5.2+43a9be4 features: Basic-Auth GSSAPI Kerberos SPNEGO How reproducible: Steps to Reproduce: 1. Add "--disable proxy" to /etc/sysconfig/atomic-openshift-node file 2. systemctl restart atomic-openshift-node.service Actual results: Node service can't start Expected results: Iptables-based proxy is disabled and node service starts normally Additional info: Similar issue: https://github.com/openshift/origin/issues/14244
There is a stack trace in the referenced issue: https://github.com/openshift/origin/issues/14244#issuecomment-302656375 Unfortunately it is just a lot of reflector calls. The only hint is that it seems to happen every second. I just brought up a 3.5 cluster with nothing in it an couldn't recreate. Likely because I didn't have an resources populating it.
Andrew, I would begin by starting an openshift cluster with the node having "--disable proxy" and trying to recreate on 3.5.5.31.
I am able to reproduce and I am testing the following fix: https://github.com/frobware/origin/tree/fix-node-panic-with-disable-proxy-bugzilla-1484272
https://github.com/openshift/ose/pull/866
Tested with ocp build v3.5.5.31.34 The openshift node service can run well with disable the proxy component. [root@ip-172-18-8-60 ~]# ps -ef | grep node-config root 52911 1 3 04:33 ? 00:00:04 /usr/bin/openshift start node --config=/etc/origin/node/node-config.yaml --loglevel=2 --disable proxy root 53648 52182 0 04:35 pts/0 00:00:00 grep --color=auto node-config [root@ip-172-18-8-60 ~]# [root@ip-172-18-8-60 ~]# systemctl status atomic-openshift-node ● atomic-openshift-node.service - Atomic OpenShift Node Loaded: loaded (/usr/lib/systemd/system/atomic-openshift-node.service; enabled; vendor preset: disabled) Drop-In: /usr/lib/systemd/system/atomic-openshift-node.service.d └─openshift-sdn-ovs.conf Active: active (running) since Thu 2017-10-12 04:33:11 EDT; 2min 40s ago Docs: https://github.com/openshift/origin Main PID: 52911 (openshift) Memory: 46.0M CGroup: /system.slice/atomic-openshift-node.service ├─52911 /usr/bin/openshift start node --config=/etc/origin/node/node-config.yaml --loglev... └─52974 journalctl -k -f
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:3049