Bug 1388893
| Summary: | SetupNetworkError: "Failed to setup network for pod ... | ||
|---|---|---|---|
| Product: | OKD | Reporter: | Jaroslav Henner <jhenner> |
| Component: | Networking | Assignee: | Ben Bennett <bbennett> |
| Status: | CLOSED DUPLICATE | QA Contact: | Meng Bo <bmeng> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.x | CC: | aos-bugs, eparis, rcyriac |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-10-26 18:29:54 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Wow. I have quite a lot of ports there!
[cloud-user@ose3-master-9pc35 ~]$ sudo ovs-vsctl show | wc -l
17070
[cloud-user@ose3-master-9pc35 ~]$ sudo ovs-vsctl show | head
a2f557de-2aea-4daf-aaf9-79c5d94a5d9a
Bridge "br0"
fail_mode: secure
Port "veth97581375"
Interface "veth97581375"
error: "could not open network device veth97581375 (No such device)"
Port "veth7988f8d0"
Interface "veth7988f8d0"
error: "could not open network device veth7988f8d0 (No such device)"
Port "veth57934955"
In the journal of the node, I can see the tenant_id is empty:
říj 26 07:26:55 ose3-master-9pc35 atomic-openshift-node[3414]: E1026 07:26:55.894660 3414 cni.go:255] Error adding network: CNI request failed with status 400: 'error running network setup script:
říj 26 07:26:55 ose3-master-9pc35 atomic-openshift-node[3414]: hostVethName veth5a20fae3, contVethMac f2:d3:0a:66:89:1d, podIP 10.1.2.251, podConfig &plugin.PodConfig{vnid:"", ingressBandwidth:"", egressBandwidth:"", wantMacvlan:false}
říj 26 07:26:55 ose3-master-9pc35 atomic-openshift-node[3414]: + lock_file=/var/lock/openshift-sdn.lock
říj 26 07:26:55 ose3-master-9pc35 atomic-openshift-node[3414]: + action=setup
říj 26 07:26:55 ose3-master-9pc35 atomic-openshift-node[3414]: + veth_host=veth5a20fae3
říj 26 07:26:55 ose3-master-9pc35 atomic-openshift-node[3414]: + macaddr=f2:d3:0a:66:89:1d
říj 26 07:26:55 ose3-master-9pc35 atomic-openshift-node[3414]: + ipaddr=10.1.2.251
říj 26 07:26:55 ose3-master-9pc35 atomic-openshift-node[3414]: + tenant_id=
říj 26 07:26:55 ose3-master-9pc35 atomic-openshift-node[3414]: + ingress_bw=
říj 26 07:26:55 ose3-master-9pc35 atomic-openshift-node[3414]: + egress_bw=
říj 26 07:26:55 ose3-master-9pc35 atomic-openshift-node[3414]: + macvlan=
říj 26 07:26:55 ose3-master-9pc35 atomic-openshift-node[3414]: + lockwrap run
říj 26 07:26:55 ose3-master-9pc35 atomic-openshift-node[3414]: + flock 200
říj 26 07:26:55 ose3-master-9pc35 atomic-openshift-node[3414]: + run
říj 26 07:26:55 ose3-master-9pc35 atomic-openshift-node[3414]: + case "$action" in
říj 26 07:26:55 ose3-master-9pc35 atomic-openshift-node[3414]: + add_ovs_port
říj 26 07:26:55 ose3-master-9pc35 atomic-openshift-node[3414]: + ovs-vsctl add-port br0 veth5a20fae3
říj 26 07:26:55 ose3-master-9pc35 atomic-openshift-node[3414]: + add_ovs_flows
říj 26 07:26:55 ose3-master-9pc35 atomic-openshift-node[3414]: ++ ovs-vsctl get Interface veth5a20fae3 ofport
říj 26 07:26:55 ose3-master-9pc35 atomic-openshift-node[3414]: + ovs_port=5583
říj 26 07:26:55 ose3-master-9pc35 atomic-openshift-node[3414]: + '[' -z 5583 ']'
říj 26 07:26:55 ose3-master-9pc35 atomic-openshift-node[3414]: + ovs-ofctl -O OpenFlow13 add-flow br0 'table=2, priority=100, in_port=5583, arp, nw_src=10.1.2.251, arp_sha=f2:d3:0a:66:89:1d, actions=load:->NXM_NX_REG0[], goto_table:5'
říj 26 07:26:55 ose3-master-9pc35 atomic-openshift-node[3414]: + ovs-ofctl -O OpenFlow13 add-flow br0 'table=2, priority=100, in_port=5583, ip, nw_src=10.1.2.251, actions=load:->NXM_NX_REG0[], goto_table:3'
říj 26 07:26:55 ose3-master-9pc35 atomic-openshift-node[3414]: + ovs-ofctl -O OpenFlow13 add-flow br0 'table=6, priority=100, arp, nw_dst=10.1.2.251, actions=output:5583'
říj 26 07:26:55 ose3-master-9pc35 atomic-openshift-node[3414]: + '[' = 0 ']'
říj 26 07:26:55 ose3-master-9pc35 atomic-openshift-node[3414]: /usr/bin/openshift-sdn-ovs: line 49: [: =: unary operator expected
*** This bug has been marked as a duplicate of bug 1388839 *** |
Description of problem: oc deploy router fails. In the journal I can see říj 26 07:26:55 ose3-master-9pc35 atomic-openshift-node[3414]: /usr/bin/openshift-sdn-ovs: line 49: [: =: unary operator expected The line 49 is: if [ $tenant_id = "0" ]; then so the tenant id is undefined or empty. Version-Release number of selected component (if applicable): atomic-openshift-sdn-ovs-3.4.0.15-1.git.0.9c963ec.el7.x86_64 atomic-openshift-3.4.0.15-1.git.0.9c963ec.el7.x86_64 How reproducible: 2/2 Steps to Reproduce: We have an automation for that, but I think the critical steps are 1. Deploy openshift 2. oc deploy router 3. Actual results: [cloud-user@ose3-master-9pc35 ~]$ oc get pods NAME READY STATUS RESTARTS AGE docker-registry-2-deploy 0/1 DeadlineExceeded 0 8h registry-console-1-deploy 0/1 DeadlineExceeded 0 8h router-1-deploy 0/1 ContainerCreating 0 6m errors in sudo journalctl -fu atomic-openshift-node.service Expected results: router and other pods deployed Additional info: