Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-17248

Pods stuck in "ContainerCreating" in a dual stack cluster: failed to configure pod interface: failed to add pod route 10.132.0.0/14 via 10.134.0.1: file exists

XMLWordPrintable

    • Critical
    • No
    • SDN Sprint 240, SDN Sprint 241
    • 2
    • Approved
    • False
    • Hide

      None

      Show
      None
    • Hide
      8/21: green - internal test good; Modified
      8/16: seen on dual stack clusters, not seen on single stack clusters; 4.14 pre-GA blocking for now; successfully tested custom payload while fix makes it u/s
      Show
      8/21: green - internal test good; Modified 8/16: seen on dual stack clusters, not seen on single stack clusters; 4.14 pre-GA blocking for now; successfully tested custom payload while fix makes it u/s

      Description of problem:

      On a dual stack cluster pods may get stuck in "ContainerCreating" status, kubelete reporting:

Warning  FailedCreatePodSandBox  4s (x8 over 92s)  kubelet  (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_dns-default-zj4kw_openshift-dns_3d728e36-28fd-4bae-818a-139ffaa17655_0(ec3c1c5eb68cfa4e20bb589907af35a2734f6492a1b741344437e4be2abc111f): error adding pod openshift-dns_dns-default-zj4kw to CNI network "multus-cni-network": plugin type="multus" name="multus-cni-network" failed (add): [openshift-dns/dns-default-zj4kw/3d728e36-28fd-4bae-818a-139ffaa17655:ovn-kubernetes]: error adding container to network "ovn-kubernetes": CNI request failed with status 400: '[openshift-dns/dns-default-zj4kw ec3c1c5eb68cfa4e20bb589907af35a2734f6492a1b741344437e4be2abc111f network default NAD default] [openshift-dns/dns-default-zj4kw ec3c1c5eb68cfa4e20bb589907af35a2734f6492a1b741344437e4be2abc111f network default NAD default] failed to configure pod interface: failed to add pod route 10.132.0.0/14 via 10.134.0.1: file exists

      Version-Release number of selected component (if applicable):

      4.14.0-ec.4

      How reproducible:

      100%

      Steps to Reproduce:

      1. Deploy dual stack cluster
2. Installation may not complete successfully since some of the pods are stuck in "ContainerCreating" status 
3. If installation succeeds then the issue can be reproduced by rebooting one of the nodes

      Actual results:

      Pods stuck in ContainerCreating

      Expected results:

      Pods start without issues

      Additional info:

      Attaching sosreport from the node where pods with the issues are scheduled  and must-gather.

Pods can start successfully after deletion/re-creation.

              ffernand@redhat.com Flavio Fernandes (Inactive)
              mcornea@redhat.com Marius Cornea
              Huiran Wang Huiran Wang
              Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

                Created:
                Updated: