We saw some deletion failures on fresly-rebooted nodes: Apr 30 10:37:18 ip-10-0-128-167 crio[2574]: 2019-04-30T10:37:18Z [verbose] Del: openshift-console:downloads-986db4698-n6qkw:openshift-sdn:eth0 {"cniVersion":"0.3.1","name":"openshift-sdn","type":"openshift-sdn"} Apr 30 10:37:18 ip-10-0-128-167 crio[2574]: 2019-04-30T10:37:18Z [error] Multus: error in invoke Delegate del - "openshift-sdn": failed to send CNI request: Post http://dummy/: dial unix /var/run/openshift-sdn/cni-server.sock: connect: no such file or directory Apr 30 10:37:18 ip-10-0-128-167 crio[2574]: time="2019-04-30 10:37:18.761334406Z" level=error msg="Error deleting network: Multus: error in invoke Delegate del - "openshift-sdn": failed to send CNI request: Post http://dummy/: dial unix /var/run/openshift-sdn/cni-server.sock: connect: no such file or directory We should be deleting both the openshift-sdn and multus configuration files on boot. Then, multus waits for openshift-sdn to come up before writing its own configuration file.
I also noticed that our current file that removes the openshift-sdn file is broken due to a directory change.
filed https://github.com/openshift/machine-config-operator/pull/685
Tested on 4.1.0-0.nightly-2019-05-08-065958 There is no such error on the node boot up
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-2019:0758