This points to a Kubernetes issue.

Check the rancher GUI to make sure all the hosts are "Active"  particularly 
nodes 0, 1, 2,3, 4 which host the separate k8 control plane for etcd and orch.

I'm not sure I have a great repair for this situation. Finding the hung host VM 
and restarting it can sometimes help.

Make sure you are using the VM sizes and number of K8 hosts we use in the 
integration/deployment directory (I suspect you are already since I think you 
run windriver)

Brian


From: [email protected] <[email protected]> On Behalf Of 
Yan Yang
Sent: Friday, February 22, 2019 2:23 AM
To: [email protected]
Subject: [onap-discuss] [oom][integration] NetworkPlugin cni failed to teardown 
pod network: failed to get IP addresses for "eth0"

Hi all,

When we install ONAP, some pods status are always in ContainerCreating,  when 
describe pod , it shows failed to get IP addresses for "eth0": <nil>, Have you 
ever encountered such issue, it would be great help if you could provide a 
solution.

Following is the error we can see when execute describe pod:

root@oom-mr02-rancher:/home/ubuntu# kubectl -n onap get pod|grep vfc-db
dev-vfc-vfc-db-67c574f5d5-tdp8l                               0/1       
ContainerCreating   0          1d
root@oom-mr02-rancher:/home/ubuntu# kubectl -n onap describe pod 
dev-vfc-vfc-db-67c574f5d5-tdp8l
Name:           dev-vfc-vfc-db-67c574f5d5-tdp8l
Namespace:      onap
Node:           mr02-node5/
Start Time:     Thu, 21 Feb 2019 06:37:05 +0000
Labels:         app=vfc-db
                pod-template-hash=2371309181
                release=dev-vfc
Annotations:    <none>
Status:         Pending
IP:
Controlled By:  ReplicaSet/dev-vfc-vfc-db-67c574f5d5
Containers:
  vfc-db:
    Container ID:
    Image:          172.30.1.66:10001/onap/vfc/db:1.2.1
    Image ID:
    Ports:          3306/TCP, 6379/TCP
    Host Ports:     0/TCP, 0/TCP
    State:          Waiting
      Reason:       ContainerCreating
    Ready:          False
    Restart Count:  0
    Limits:
      cpu:     200m
      memory:  500Mi
    Requests:
      cpu:      100m
      memory:   250Mi
    Liveness:   tcp-socket :3306 delay=120s timeout=1s period=10s #success=1 
#failure=3
    Readiness:  tcp-socket :3306 delay=120s timeout=1s period=10s #success=1 
#failure=3
    Environment:
      MSB_ADDR:  msb-iag:80
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-2jggr 
(ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  default-token-2jggr:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-2jggr
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason                  Age                  From                 
Message
  ----     ------                  ----                 ----                 
-------
  Warning  FailedCreatePodSandBox  59s (x1395 over 1d)  kubelet, mr02-node5  
(combined from similar events): Failed create pod sandbox: rpc error: code = 
Unknown desc = [failed to set up sandbox container 
"5633aa75c314e25b6b8be755e9290c4058c09ae4b815c2666ecfd2fcb320f435" network for 
pod "dev-vfc-vfc-db-67c574f5d5-tdp8l": NetworkPlugin cni failed to set up pod 
"dev-vfc-vfc-db-67c574f5d5-tdp8l_onap" network: No MAC address found, failed to 
clean up sandbox container 
"5633aa75c314e25b6b8be755e9290c4058c09ae4b815c2666ecfd2fcb320f435" network for 
pod "dev-vfc-vfc-db-67c574f5d5-tdp8l": NetworkPlugin cni failed to teardown pod 
"dev-vfc-vfc-db-67c574f5d5-tdp8l_onap" network: failed to get IP addresses for 
"eth0": <nil>]


Best Regards,
Yan


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#15694): https://lists.onap.org/g/onap-discuss/message/15694
Mute This Topic: https://lists.onap.org/mt/29995983/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to