Yang, Looks like all the errors are secondary - pods like filebeat trying to attach as a sidecar etc... except the CNI networking one - this one looks like there is an issue with either your k8s network or your general system. How does the rest of the k8s system look like besides multicloud - the pods of the kubernetes system itself and any other onap pod
Warning FailedCreatePodSandBox 5m kubelet, oom-k8s-01 Failed create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "c0f1d62147a1516face58d13d4249603ac1411a9054a2911908e6d6309e8592d" network for pod "dev-multicloud-multicloud-7cd96f75fb-pnvnk": NetworkPlugin cni failed to set up pod "dev-multicloud-multicloud-7cd96f75fb-pnvnk_onap" network: failed to lookup "eth0": Link not found /michael From: [email protected] <[email protected]> On Behalf Of Ukponmwan, Itohan Sent: Monday, November 26, 2018 3:19 PM To: Yang, Bin <[email protected]>; Huang, Haibin <[email protected]>; [email protected] Cc: ONAP Dev Team <[email protected]> Subject: [onap-discuss] Multicloud pod restart fails Hi All, I am trying to restart the multicloud pods in SB06 but it fails. I also tried to redeploy multicloud but I see the same error in both cases. root@oom-rancher:~/oom/kubernetes# kubectl get pods -n onap |grep multicloud dev-multicloud-multicloud-7cd96f75fb-pnvnk 0/2 CrashLoopBackOff 12 8m dev-multicloud-multicloud-azure-85548b6469-5vzhb 0/2 RunContainerError 12 8m dev-multicloud-multicloud-ocata-85d796889b-nd84h 0/2 RunContainerError 8 8m dev-multicloud-multicloud-pike-78fb779f6c-f57d4 0/2 CrashLoopBackOff 12 8m dev-multicloud-multicloud-vio-794f8b7d85-v55h5 0/2 CrashLoopBackOff 12 8m dev-multicloud-multicloud-windriver-6ffb4dcd-sxhb5 0/2 CrashLoopBackOff 12 8m I also did a describe on the multicloud pod but I see the following error in the events section; Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 6m default-scheduler Successfully assigned onap/dev-multicloud-multicloud-7cd96f75fb-pnvnk to oom-k8s-01 Normal Pulling 6m kubelet, oom-k8s-01 pulling image "10.12.5.2:5000/onap/multicloud/framework:1.2.1" Normal Pulled 5m kubelet, oom-k8s-01 Successfully pulled image "10.12.5.2:5000/onap/multicloud/framework:1.2.1" Warning Failed 5m kubelet, oom-k8s-01 Error: failed to start container "multicloud": Error response from daemon: cannot join network of a non running container: 59bc093121a656543822c8fae1748f18c1594038f93b4c3ba439fb6bb7586a14 Warning Failed 5m kubelet, oom-k8s-01 Error: failed to start container "filebeat-onap": Error response from daemon: cannot join network of a non running container: 59bc093121a656543822c8fae1748f18c1594038f93b4c3ba439fb6bb7586a14 Warning Failed 5m kubelet, oom-k8s-01 Error: failed to start container "multicloud": Error response from daemon: cannot join network of a non running container: 8f63e4e23e85c0543996691fa863245dc6a1ac03f6803e0e7585bc9df64a4c40 Warning Failed 5m kubelet, oom-k8s-01 Error: failed to start container "filebeat-onap": Error response from daemon: cannot join network of a non running container: 8f63e4e23e85c0543996691fa863245dc6a1ac03f6803e0e7585bc9df64a4c40 Warning FailedCreatePodSandBox 5m kubelet, oom-k8s-01 Failed create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "c0f1d62147a1516face58d13d4249603ac1411a9054a2911908e6d6309e8592d" network for pod "dev-multicloud-multicloud-7cd96f75fb-pnvnk": NetworkPlugin cni failed to set up pod "dev-multicloud-multicloud-7cd96f75fb-pnvnk_onap" network: failed to lookup "eth0": Link not found Warning Failed 5m kubelet, oom-k8s-01 Error: failed to start container "multicloud": Error response from daemon: cannot join network of a non running container: fa5cd9c1b222be0f3dafb5d1c598ac6cfc3f504669d6984a03c200908ace195a Normal Pulled 5m (x2 over 5m) kubelet, oom-k8s-01 Container image "10.12.5.2:5000/onap/multicloud/framework:1.2.1" already present on machine Normal Created 5m (x3 over 5m) kubelet, oom-k8s-01 Created container Normal Created 5m (x3 over 5m) kubelet, oom-k8s-01 Created container Normal Pulled 5m (x3 over 5m) kubelet, oom-k8s-01 Container image "docker.elastic.co/beats/filebeat:5.5.0" already present on machine Warning Failed 5m kubelet, oom-k8s-01 Error: failed to start container "filebeat-onap": Error response from daemon: cannot join network of a non running container: fa5cd9c1b222be0f3dafb5d1c598ac6cfc3f504669d6984a03c200908ace195a Warning BackOff 4m kubelet, oom-k8s-01 Back-off restarting failed container Normal SandboxChanged 1m (x15 over 5m) kubelet, oom-k8s-01 Pod sandbox changed, it will be killed and re-created. Has anyone see this error? Thanks, Itohan This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service <https://www.amdocs.com/about/email-terms-of-service> -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14087): https://lists.onap.org/g/onap-discuss/message/14087 Mute This Topic: https://lists.onap.org/mt/28324888/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
