{"action":"closed","issue":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/65544","repository_url":"https://api.github.com/repos/kubernetes/kubernetes","labels_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/65544/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/65544/comments","events_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/65544/events","html_url":"https://github.com/kubernetes/kubernetes/issues/65544","id":336348331,"node_id":"MDU6SXNzdWUzMzYzNDgzMzE=","number":65544,"title":"Failed to create Sandbox CNI when creating AWS EKS Cluster via Terraform","user":{"login":"akhilyendluri","id":13486835,"node_id":"MDQ6VXNlcjEzNDg2ODM1","avatar_url":"https://avatars2.githubusercontent.com/u/13486835?v=4","gravatar_id":"","url":"https://api.github.com/users/akhilyendluri","html_url":"https://github.com/akhilyendluri","followers_url":"https://api.github.com/users/akhilyendluri/followers","following_url":"https://api.github.com/users/akhilyendluri/following{/other_user}","gists_url":"https://api.github.com/users/akhilyendluri/gists{/gist_id}","starred_url":"https://api.github.com/users/akhilyendluri/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/akhilyendluri/subscriptions","organizations_url":"https://api.github.com/users/akhilyendluri/orgs","repos_url":"https://api.github.com/users/akhilyendluri/repos","events_url":"https://api.github.com/users/akhilyendluri/events{/privacy}","received_events_url":"https://api.github.com/users/akhilyendluri/received_events","type":"User","site_admin":false},"labels":[{"id":617149945,"node_id":"MDU6TGFiZWw2MTcxNDk5NDU=","url":"https://api.github.com/repos/kubernetes/kubernetes/labels/needs-sig","name":"needs-sig","color":"ededed","default":false}],"state":"closed","locked":false,"assignee":{"login":"dims","id":23304,"node_id":"MDQ6VXNlcjIzMzA0","avatar_url":"https://avatars2.githubusercontent.com/u/23304?v=4","gravatar_id":"","url":"https://api.github.com/users/dims","html_url":"https://github.com/dims","followers_url":"https://api.github.com/users/dims/followers","following_url":"https://api.github.com/users/dims/following{/other_user}","gists_url":"https://api.github.com/users/dims/gists{/gist_id}","starred_url":"https://api.github.com/users/dims/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dims/subscriptions","organizations_url":"https://api.github.com/users/dims/orgs","repos_url":"https://api.github.com/users/dims/repos","events_url":"https://api.github.com/users/dims/events{/privacy}","received_events_url":"https://api.github.com/users/dims/received_events","type":"User","site_admin":false},"assignees":[{"login":"dims","id":23304,"node_id":"MDQ6VXNlcjIzMzA0","avatar_url":"https://avatars2.githubusercontent.com/u/23304?v=4","gravatar_id":"","url":"https://api.github.com/users/dims","html_url":"https://github.com/dims","followers_url":"https://api.github.com/users/dims/followers","following_url":"https://api.github.com/users/dims/following{/other_user}","gists_url":"https://api.github.com/users/dims/gists{/gist_id}","starred_url":"https://api.github.com/users/dims/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dims/subscriptions","organizations_url":"https://api.github.com/users/dims/orgs","repos_url":"https://api.github.com/users/dims/repos","events_url":"https://api.github.com/users/dims/events{/privacy}","received_events_url":"https://api.github.com/users/dims/received_events","type":"User","site_admin":false}],"milestone":null,"comments":7,"created_at":"2018-06-27T18:56:34Z","updated_at":"2018-07-31T23:15:30Z","closed_at":"2018-07-31T23:15:30Z","author_association":"NONE","body":"Hi,\r\n@kubernetes/sig-contributor-experience-test-failures\r\nI am facing a similar issue. \r\n\r\nI created a cluster in aws eks using terraform script given in https://www.terraform.io/docs/providers/aws/guides/eks-getting-started.html#guide-overview\r\n\r\nAfter this I was deploying the guestbook application as given in  https://docs.aws.amazon.com/eks/latest/userguide/getting-started.html \r\n\r\nOnce my pods got created I noticed that they where not ready. I saw this in my\r\n` kubectl describe pods`\r\n\r\n``` \r\nName:           redis-master-8rqtb\r\nNamespace:      default\r\nNode:           ip-10-0-0-232.ec2.internal/10.0.0.232\r\nStart Time:     Tue, 26 Jun 2018 13:18:22 -0400\r\nLabels:         app=redis\r\n                role=master\r\nAnnotations:    <none>\r\nStatus:         Pending\r\nIP:\r\nControlled By:  ReplicationController/redis-master\r\nContainers:\r\n  redis-master:\r\n    Container ID:\r\n    Image:          redis:2.8.23\r\n    Image ID:\r\n    Port:           6379/TCP\r\n    Host Port:      0/TCP\r\n    State:          Waiting\r\n      Reason:       ContainerCreating\r\n    Ready:          False\r\n    Restart Count:  0\r\n    Environment:    <none>\r\n    Mounts:\r\n      /var/run/secrets/kubernetes.io/serviceaccount from default-token-4xr62 (ro)\r\nConditions:\r\n  Type           Status\r\n  Initialized    True\r\n  Ready          False\r\n  PodScheduled   True\r\nVolumes:\r\n  default-token-4xr62:\r\n    Type:        Secret (a volume populated by a Secret)\r\n    SecretName:  default-token-4xr62\r\n    Optional:    false\r\nQoS Class:       BestEffort\r\nNode-Selectors:  <none>\r\nTolerations:     node.kubernetes.io/not-ready:NoExecute for 300s\r\n                 node.kubernetes.io/unreachable:NoExecute for 300s\r\n\r\n Events:\r\n Type                       Reason                  Age                  From                                        Message\r\n\r\n Warning  FailedCreatePodSandBox     32m       kubelet, ip-10-0-0-232.ec2.internal   Failed create pod sandbox: rpc error: code = Unknown desc = NetworkPlugin cni failed to set up pod \"redis-master-8rqtb_default\" network: rpc error: code = Unavailable desc = grpc: the connection is unavailable\r\n Normal   SandboxChanged          2m (x2994 over 1h)   kubelet, ip-10-0-0-232.ec2.internal  Pod sandbox changed, it will be killed and re-created.\r\n```\r\n\r\nI tried adding flannel using `kubectl apply -f kube-flannel.yml` \r\n\r\nEven then I was not getting the issue.\r\n\r\nI tried to use `journalctl -u kubelet` to get the kubelet logs. But the logs where empty.\r\n\r\n`akhil@ubuntu:~$ kubectl version --short\r\n`\r\n\r\n```\r\nClient Version: v1.10.3\r\nServer Version: v1.10.3\r\n```\r\n\r\n`akhil@ubuntu:~$ uname -a`\r\n\r\n```\r\nLinux ubuntu 4.4.0-87-generic #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux\r\n```\r\n\r\n`akhil@ubuntu:~$ kubectl get pods --all-namespaces`\r\n\r\n```\r\nNAMESPACE     NAME                        READY     STATUS              RESTARTS   AGE\r\ndefault       redis-master-8rqtb          0/1       ContainerCreating   0          1h\r\nkube-system   aws-node-28gkv              0/1       CrashLoopBackOff    18         1h\r\nkube-system   aws-node-bfvf2              0/1       CrashLoopBackOff    18         1h\r\nkube-system   aws-node-kn759              0/1       CrashLoopBackOff    18         1h\r\nkube-system   kube-dns-64b69465b4-b8p84   0/3       ContainerCreating   0          2h\r\nkube-system   kube-proxy-5686g            1/1       Running             0          1h\r\nkube-system   kube-proxy-hwd29            1/1       Running             0          1h\r\nkube-system   kube-proxy-m5854            1/1       Running             0          1h\r\n```\r\n\r\nWhen I tried getting the logs\r\n\r\n`akhil@ubuntu:~$ journalctl -u kubelet`\r\n\r\nI got\r\n\r\n```\r\n-- No entries --\r\n```\r\n\r\nAlso running `kubectl logs aws-node-bfvf2 -n kube-system`\r\n```\r\n=====Starting installing AWS-CNI =========\r\n=====Starting amazon-k8s-agent ===========\r\nERROR: logging before flag.Parse: W0626 19:18:29.099664      14 client_config.go:533] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.\r\n\r\n```\r\n"}}
{"actor":{"display_login":"k8s-ci-robot"}}