-
Bug
-
Resolution: Won't Do
-
High
-
None
-
Casablanca Release
-
None
I redeployed multicloud but the pods are stuck in crashloopbackoff state. I do a describe on one of the pods and I see the following error;
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 33m default-scheduler Successfully assigned onap/dev-multicloud-multicloud-7cd96f75fb-fmxg5 to oom-k8s-09
Normal Pulling 32m kubelet, oom-k8s-09 pulling image "10.12.5.2:5000/onap/multicloud/framework:1.2.1"
Normal Pulled 32m kubelet, oom-k8s-09 Successfully pulled image "10.12.5.2:5000/onap/multicloud/framework:1.2.1"
Warning Failed 32m kubelet, oom-k8s-09 Error: failed to start container "multicloud": Error response from daemon: cannot join network of a non running container: f4ab81b0b99e4b2d3e81a15da769fe3ad6403964a886925029d7fda9e3d55746
Warning Failed 32m kubelet, oom-k8s-09 Error: failed to start container "filebeat-onap": Error response from daemon: cannot join network of a non running container: f4ab81b0b99e4b2d3e81a15da769fe3ad6403964a886925029d7fda9e3d55746
Warning Failed 32m kubelet, oom-k8s-09 Error: failed to start container "filebeat-onap": Error response from daemon: cannot join network of a non running container: 7c6ae94527bb192cb630ad3c6a18877f2bb6c2c68072ba4a390acca8f5349b50
Warning Failed 32m kubelet, oom-k8s-09 Error: failed to start container "multicloud": Error response from daemon: cannot join network of a non running container: 7c6ae94527bb192cb630ad3c6a18877f2bb6c2c68072ba4a390acca8f5349b50
Warning Failed 32m kubelet, oom-k8s-09 Error: failed to start container "multicloud": Error response from daemon: cannot join network of a non running container: ed8c5344d69d9e6e51c8ee1aaaa11573135e442dceacf433098c294902444e47
Normal Created 32m (x3 over 32m) kubelet, oom-k8s-09 Created container
Normal Pulled 32m (x2 over 32m) kubelet, oom-k8s-09 Container image "10.12.5.2:5000/onap/multicloud/framework:1.2.1" already present on machine
Normal Pulled 32m (x3 over 32m) kubelet, oom-k8s-09 Container image "docker.elastic.co/beats/filebeat:5.5.0" already present on machine
Normal Created 32m (x3 over 32m) kubelet, oom-k8s-09 Created container
Warning Failed 32m kubelet, oom-k8s-09 Error: failed to start container "filebeat-onap": Error response from daemon: cannot join network of a non running container: ed8c5344d69d9e6e51c8ee1aaaa11573135e442dceacf433098c294902444e47
Normal SandboxChanged 17m (x67 over 32m) kubelet, oom-k8s-09 Pod sandbox changed, it will be killed and re-created.
Warning BackOff 7m (x81 over 32m) kubelet, oom-k8s-09 Back-off restarting failed container
Warning BackOff 2m (x94 over 32m) kubelet, oom-k8s-09 Back-off restarting failed container
- mentioned in
-
Page Loading...