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

Pod stuck in containerCreating state when the node on which it is running is Terminated

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • 4.13, 4.12.0, 4.11.z, 4.10.z
    • Networking / ovn-kubernetes
    • None
    • Critical
    • None
    • SDN Sprint 228
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Bug Fix
    • Done

      Description of problem:

      The alertmanager pod is stuck on OCP 4.11 with OVN in container Creating State

From oc describe alertmanager pod:
...
Events:
  Type     Reason                  Age                  From     Message
  ----     ------                  ----                 ----     -------
  Warning  FailedCreatePodSandBox  16s (x459 over 17h)  kubelet  (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_alertmanager-managed-ocs-alertmanager-0_openshift-storage_3a55ed54-4eaa-4f65-8a10-e5d21fad1ebc_0(88575547dc0b210307b89dd2bb8e379ece0962b607ac2707a1c2cf630b1aaa78): error adding pod openshift-storage_alertmanager-managed-ocs-alertmanager-0 to CNI network "multus-cni-network": plugin type="multus" name="multus-cni-network" failed (add): [openshift-storage/alertmanager-managed-ocs-alertmanager-0/3a55ed54-4eaa-4f65-8a10-e5d21fad1ebc:ovn-kubernetes]: error adding container to network "ovn-kubernetes": CNI request failed with status 400: '[openshift-storage/alertmanager-managed-ocs-alertmanager-0 88575547dc0b210307b89dd2bb8e379ece0962b607ac2707a1c2cf630b1aaa78] [openshift

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

      OCP 4.11 with OVN

      How reproducible:

      100%

      Steps to Reproduce:

      1. Terminate the node on which alertmanager pod is running
2. pod will get stuck in container Creating state
3.

      Actual results:

      AlertManager pod is stuck in container Creating state

      Expected results:

      Alertmanager pod is ready

      Additional info:

      The workaround would be to terminate the alertmanager pod

              ffernand@redhat.com Flavio Fernandes (Inactive)
              resoni@redhat.com Rewant Soni
              Anurag Saxena Anurag Saxena
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: