contiv
Contiv stops working after reboot of the master
Everything was working fine but when i rebooted the master, contiv did not come up.
contiv version: 1.0.3
k8s version:
[hemakuma@K8S-1 ~]$ kc version
Client Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.6", GitCommit:"7fa1c1756d8bc963f1a389f4a6937dc71f08ada2", GitTreeState:"clean", BuildDate:"2017-06-16T18:34:20Z", GoVersion:"go1.7.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.6", GitCommit:"7fa1c1756d8bc963f1a389f4a6937dc71f08ada2", GitTreeState:"clean", BuildDate:"2017-06-16T18:21:54Z", GoVersion:"go1.7.6", Compiler:"gc", Platform:"linux/amd64"}
contiv running as binary or from container ? from container host os ? Centos 7 with Firewalld and selinux turn disabled.
I tired with a fresh new install. it works on the first install but when i a reboot, contiv containers never comes up, it goes on the CrashLoopBackOFF state.
[hemakuma@K8S-1 contiv-1.0.3]$ kcs NAME READY STATUS RESTARTS AGE contiv-api-proxy-888g4 0/1 CrashLoopBackOff 6 7m contiv-etcd-484pg 1/1 Running 4 45m contiv-netmaster-1gvxm 0/1 CrashLoopBackOff 6 7m contiv-netplugin-7hkcl 0/1 CrashLoopBackOff 6 7m contiv-netplugin-lsl2x 0/1 CrashLoopBackOff 6 7m contiv-netplugin-wwgj9 0/1 CrashLoopBackOff 6 7m etcd-k8s-1 1/1 Running 2 20h kube-apiserver-k8s-1 1/1 Running 2 20h kube-controller-manager-k8s-1 1/1 Running 2 20h kube-dns-692378583-j18hd 0/3 Error 0 20h kube-proxy-6z1qk 1/1 Running 0 18h kube-proxy-c9ddc 1/1 Running 0 20h kube-proxy-z4txq 1/1 Running 2 20h kube-scheduler-k8s-1 1/1 Running 2 20h kubernetes-dashboard-2039414953-wnd6f 0/1 CrashLoopBackOff 98 8h
I tried to uninstall but got the following error: The connection to the server localhost:8080 was refused - did you specify the right host or port?
please provide details. Its impossible to know your problem by the description you have provided.
contiv version k8s version contiv running as binary or from container ? host os ?
