Description of problem: Error about 'failed to create macvlan interface' appears in the result of `oc describe po` and node log when trying to create egress router with ose-egress-router image. Version-Release number of selected component (if applicable): openshift v3.4.0.16+cc70b72 kubernetes v1.4.0+776c994 etcd 3.1.0-rc.0 How reproducible: always Steps to Reproduce: 1. Setup multi node env 2. Given the privileged permission to the user 3. Create the egress router via the user with image openshift3/ose-egress-router:v3.4.0.16 $ oc create -f https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/networking/egress-ingress/egress-router-list.json 4. Describe the pod 5. Check the node log Actual results: 4. FirstSeen LastSeen Count From SubobjectPath Type Reason Message --------- -------- ----- ---- ------------- -------- ------ ------- 12m 12m 1 {default-scheduler } Normal Scheduled Successfully assigned egress-rc-x48cm to ose-node1.bmeng.local 12m 12s 218 {kubelet ose-node1.bmeng.local} Warning FailedSync Error syncing pod, skipping: failed to "SetupNetwork" for "egress-rc-x48cm_u1p1" with SetupNetworkError: "Failed to setup network for pod \"egress-rc-x48cm_u1p1(550d4de2-9ce2-11e6-8f14-525400dd3698)\" using network plugins \"cni\": CNI request failed with status 400: 'failed to create macvlan interface: no such device\n'; Skipping pod" 5. Oct 28 15:58:42 ose-node1.bmeng.local atomic-openshift-node[2070]: E1028 15:58:42.677807 2070 docker_manager.go:1696] Failed to create symbolic link to the log file of pod "egress-rc-yav0a_u1p1(5c12dbaf-9ce4-11e6-8f14-525400dd3698)" container "POD": symlink /var/log/containers/egress-rc-yav0a_u1p1_POD-5f71173c5de4082ead46a60eba46d837114e58395180610d0321ac62d8848e65.log: no such file or directory Oct 28 15:58:42 ose-node1.bmeng.local atomic-openshift-node[2070]: E1028 15:58:42.728603 2070 docker_manager.go:357] NetworkPlugin cni failed on the status hook for pod 'egress-rc-yav0a' - Unexpected command output Device "eth0" does not exist. Oct 28 15:58:42 ose-node1.bmeng.local atomic-openshift-node[2070]: with error: exit status 1 Oct 28 15:58:42 ose-node1.bmeng.local atomic-openshift-node[2070]: E1028 15:58:42.794289 2070 cni.go:255] Error adding network: CNI request failed with status 400: 'failed to create macvlan interface: no such device Oct 28 15:58:42 ose-node1.bmeng.local atomic-openshift-node[2070]: ' Oct 28 15:58:42 ose-node1.bmeng.local atomic-openshift-node[2070]: E1028 15:58:42.794310 2070 cni.go:209] Error while adding to cni network: CNI request failed with status 400: 'failed to create macvlan interface: no such device Oct 28 15:58:42 ose-node1.bmeng.local atomic-openshift-node[2070]: ' Oct 28 15:58:42 ose-node1.bmeng.local atomic-openshift-node[2070]: E1028 15:58:42.794333 2070 docker_manager.go:2127] Failed to setup network for pod "egress-rc-yav0a_u1p1(5c12dbaf-9ce4-11e6-8f14-525400dd3698)" using network plugins "cni": CNI request failed with status 400: 'failed to create macvlan interface: no such device Oct 28 15:58:42 ose-node1.bmeng.local atomic-openshift-node[2070]: '; Skipping pod Oct 28 15:58:43 ose-node1.bmeng.local atomic-openshift-node[2070]: E1028 15:58:43.196433 2070 pod_workers.go:184] Error syncing pod 5c12dbaf-9ce4-11e6-8f14-525400dd3698, skipping: failed to "SetupNetwork" for "egress-rc-yav0a_u1p1" with SetupNetworkError: "Failed to setup network for pod \"egress-rc-yav0a_u1p1(5c12dbaf-9ce4-11e6-8f14-525400dd3698)\" using network plugins \"cni\": CNI request failed with status 400: 'failed to create macvlan interface: no such device\n'; Skipping pod" Oct 28 15:58:43 ose-node1.bmeng.local atomic-openshift-node[2070]: I1028 15:58:43.801468 2070 reconciler.go:299] MountVolume operation started for volume "kubernetes.io/secret/5c12dbaf-9ce4-11e6-8f14-525400dd3698-default-token-961tw" (spec.Name: "default-token-961tw") to pod "5c12dbaf-9ce4-11e6-8f14-525400dd3698" (UID: "5c12dbaf-9ce4-11e6-8f14-525400dd3698"). Volume is already mounted to pod, but remount was requested. Oct 28 15:58:43 ose-node1.bmeng.local atomic-openshift-node[2070]: I1028 15:58:43.803985 2070 operation_executor.go:802] MountVolume.SetUp succeeded for volume "kubernetes.io/secret/5c12dbaf-9ce4-11e6-8f14-525400dd3698-default-token-961tw" (spec.Name: "default-token-961tw") pod "5c12dbaf-9ce4-11e6-8f14-525400dd3698" (UID: "5c12dbaf-9ce4-11e6-8f14-525400dd3698"). Oct 28 15:58:45 ose-node1.bmeng.local atomic-openshift-node[2070]: E1028 15:58:45.240595 2070 docker_manager.go:746] Logging security options: {key:seccomp value:unconfined msg:} Oct 28 15:58:45 ose-node1.bmeng.local atomic-openshift-node[2070]: E1028 15:58:45.776127 2070 docker_manager.go:1696] Failed to create symbolic link to the log file of pod "egress-rc-yav0a_u1p1(5c12dbaf-9ce4-11e6-8f14-525400dd3698)" container "POD": symlink /var/log/containers/egress-rc-yav0a_u1p1_POD-cd6892abe94281779b14af7214791d6b89aaeb1f9cc9202d1e59fe7510bed309.log: no such file or directory Oct 28 15:58:45 ose-node1.bmeng.local atomic-openshift-node[2070]: E1028 15:58:45.825135 2070 docker_manager.go:357] NetworkPlugin cni failed on the status hook for pod 'egress-rc-yav0a' - Unexpected address output Oct 28 15:58:45 ose-node1.bmeng.local atomic-openshift-node[2070]: E1028 15:58:45.841825 2070 cni.go:255] Error adding network: CNI request failed with status 400: 'failed to create macvlan interface: no such device Oct 28 15:58:45 ose-node1.bmeng.local atomic-openshift-node[2070]: ' Oct 28 15:58:45 ose-node1.bmeng.local atomic-openshift-node[2070]: E1028 15:58:45.841865 2070 cni.go:209] Error while adding to cni network: CNI request failed with status 400: 'failed to create macvlan interface: no such device Oct 28 15:58:45 ose-node1.bmeng.local atomic-openshift-node[2070]: ' Oct 28 15:58:45 ose-node1.bmeng.local atomic-openshift-node[2070]: E1028 15:58:45.841892 2070 docker_manager.go:2127] Failed to setup network for pod "egress-rc-yav0a_u1p1(5c12dbaf-9ce4-11e6-8f14-525400dd3698)" using network plugins "cni": CNI request failed with status 400: 'failed to create macvlan interface: no such device Oct 28 15:58:45 ose-node1.bmeng.local atomic-openshift-node[2070]: '; Skipping pod Expected results: The egress router can be created and work well. Additional info:
verified in OCP 3.4.0.21, egress router pod can be created.
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:0066