[Openshift] : 4.0.2-34: Single Yaml: Pod launch is failing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juniper Openstack |
Fix Released
|
Critical
|
Savithru Lokanath | ||
R4.1 |
Fix Released
|
Critical
|
Savithru Lokanath |
Bug Description
On an Openshift cluster (brought up using Single Yaml) POD launch is failing. In /opt/cni/bin loopback binary was missing. Even after copying the same vrouter failed to fetch config in CNI log
[root@5b7s19 bin]# ls -lrt
total 8332
-rwxr-xr-x. 1 root root 5398406 Nov 6 21:52 contrail-k8s-cni
-rwxr-xr-x. 1 root root 3132224 Nov 7 17:55 loopback >>> Missing originaly
CNI Log
--------
I : 18052 : 2017/11/07 17:57:59 vrouter.go:79: VRouter request. Operation : GET Url : http://
E : 18052 : 2017/11/07 17:57:59 vrouter.go:147: Failed HTTP Get operation. Return code 404
I : 18052 : 2017/11/07 17:57:59 vrouter.go:181: Iteration 14 : Get vrouter failed
[root@5b7s19 bin]#
contrail-
-------
agerDebugLog: VncPod - Vrouter 10.87.121.36 Not Found for Pod faf55865-c360-11e7
-9119-0cc47aa89e64
11/08/2017 02:16:03 AM [contrail-
agerDebugLog: VncPod - Vrouter 10.87.121.35 Not Found for Pod a877a124-c41b-11e7
-b3db-0cc47aa89e64
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE
default docker-
default router-3-deploy 0/1 Pending 0 20h <none>
default ubuntuapp 0/1 RunContainerError 0 1h <none> 5b7s19
juniper ubuntuapp-1 0/1 ContainerCreating 0 21m <none> 5b7s20
kube-system contrail-
kube-system contrail-
kube-system contrail-
kube-system contrail-
kube-system contrail-
kube-system contrail-
summary: |
- [Openshift] : 4.0.2-34: Single Yaml: Pod launched is failing + [Openshift] : 4.0.2-34: Single Yaml: Pod launch is failing |
Changed in juniperopenstack: | |
importance: | Undecided → Critical |
assignee: | nobody → Savithru Lokanath (slokanath) |
milestone: | none → r4.0.3.0 |
information type: | Proprietary → Public |
Chhandak, after copying loopback binary to /opt/cni/bin, I noticed in your setup that the config did not have vRouter info. So I added the vRouters from the Contrail UI.
After this, the services are up. Please raise a separate bug for that & assign to Sachhin. I will fix the loopback issue in the playbook with this bug.
root@5b7s20( agent): /# contrail-status vrouter- agent initializing (No Configuration for self) vrouter- nodemgr active
== Contrail vRouter ==
supervisor-vrouter: active
contrail-
contrail-
root@5b7s18 ~]# oc get pods -o wide
NAME READY STATUS RESTARTS AGE IP NODE
ubuntuapp-1 1/1 Running 0 3m 10.47.255.250 5b7s19
ubuntuapp-2 1/1 Running 0 2m 10.47.255.249 5b7s20