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

Installation failure due to Alertmanager failing to join CNI network

XMLWordPrintable

    • +
    • No
    • 1
    • SDN Sprint 240, SDN Sprint 241
    • 2
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      A cluster installation (4.11.36) ultimately failed because an alertmanager pod could not start, and remained in a ContainerCreating state.
      
      The namespace events show:
      
      LAST SEEN   TYPE      REASON                   OBJECT                    MESSAGE                 
      3m10s       Warning   FailedCreatePodSandBox   pod/alertmanager-main-0   (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_alertmanager-main-0_openshift-monitor
      ing_ead22ae2-c67d-4e3f-a3c2-73a87a564e6d_0(6105cad796e2b51bed66b5515bf42939694dfa920395ebc72aec21cd076eab85): error adding pod openshift-monitoring_alertmanager-main-0 to CNI network "multus-cni-network": plugin type="multus" name="multus-cni-net
      work" failed (add): [openshift-monitoring/alertmanager-main-0/ead22ae2-c67d-4e3f-a3c2-73a87a564e6d:ovn-kubernetes]: error adding container to network "ovn-kubernetes": CNI request failed with status 400: '[openshift-monitoring/alertmanager-main-0
       6105cad796e2b51bed66b5515bf42939694dfa920395ebc72aec21cd076eab85] [openshift-monitoring/alertmanager-main-0 6105cad796e2b51bed66b5515bf42939694dfa920395ebc72aec21cd076eab85] failed to get pod annotation: timed out waiting for annotations: contex
      t deadline exceeded...                 
      
      Manually deleting the pod caused it to immediately recreate and run successfully.

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

      4.12.10

      How reproducible:

      Unknown

      Actual results:

      The monitoring cluster operator remains in a non-available state due to the lack of the alertmanager pod being present. The alertmanager pod never runs.

      Expected results:

      The alertmanager pod should run without needing manual intervention.

      Additional info:

       

              pepalani@redhat.com Periyasamy Palanisamy
              mbargenq Matt Bargenquast (Inactive)
              Jean Chen Jean Chen
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: