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

After cluster upgrade from 4.13.30 to 4.14.13 one of the pod stuck in CreateContainerConfigError

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 4.14.z
    • Node / Kubelet
    • Moderate
    • No
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      metal3-baremetal-operator pod stuck in CreateContainerConfigError After investigation we found that metal3-barematal-operator is using scc which is being managed by kasten operator.
      - k10-prometheus-server
      - k10-grafanaWe 
      Where as it should use hostnetwork-v2 scc.We tried to delete both the scc and the pod started as expected but again if the pod restarted it again stuck in same situation.

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

          

      How reproducible:

          n/a

      Steps to Reproduce:

      Actual results:

      metal3-baremetal-operator stuck in CreateContainerConfigError

      Expected results:

      metal3-baremetal-operator should be working as expected.

      Additional info:

          

            aos-node@redhat.com Node Team Bot Account
            rhn-support-ppradhan Pramod Pradhan
            Jad Haj Yahya Jad Haj Yahya
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: