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

[azuer]Some pods stuck in CrashLoopBackOff after enable TechPreviewNoUpgrade

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • 4.14
    • Storage / Operators
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • No
    • None
    • None
    • Proposed
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      Setup an azure cluster, and enable TechPreviewNoUpgrade, some pods stuck in CrashLoopBackOff.

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

      4.14.0-0.nightly-2023-06-26-004511

      How reproducible:

      Always

      Steps to Reproduce:

      1. Setup an azure cluster
      2. Enable TechPreviewNoUpgrade 
      $ oc edit featuregate cluster
      spec:
        featureSet: TechPreviewNoUpgrade
      3.
      

      Actual results:

      Some storage pods stuck in CrashLoopBackOff.
      $ oc get po --all-namespaces | grep -v Running    
      NAMESPACE                                          NAME                                                         READY   STATUS                  RESTARTS         AGE
      openshift-apiserver                                apiserver-854d84bdbc-ksp8r                                   0/2     Pending                 0                77m
      openshift-authentication                           oauth-openshift-76f6c9cbb4-dwv6m                             0/1     Pending                 0                77m
      openshift-cluster-csi-drivers                      azure-disk-csi-driver-controller-7fd99fc574-c2w47            0/11    Init:CrashLoopBackOff   20 (33s ago)     78m
      openshift-cluster-csi-drivers                      azure-disk-csi-driver-node-bdk52                             0/3     Init:CrashLoopBackOff   25 (60s ago)     78m
      openshift-cluster-csi-drivers                      azure-disk-csi-driver-node-jts8b                             0/3     Init:CrashLoopBackOff   18 (4m43s ago)   71m
      openshift-cluster-csi-drivers                      azure-disk-csi-driver-node-l2czp                             0/3     Init:CrashLoopBackOff   19 (2m30s ago)   74m
      openshift-cluster-csi-drivers                      azure-file-csi-driver-controller-7664dc5dd8-phhrj            0/9     Init:CrashLoopBackOff   20 (23s ago)     78m
      openshift-cluster-csi-drivers                      azure-file-csi-driver-node-5vdrw                             0/3     Init:CrashLoopBackOff   18 (4m18s ago)   71m
      openshift-cluster-csi-drivers                      azure-file-csi-driver-node-qr8s7                             0/3     Init:CrashLoopBackOff   25 (55s ago)     78m
      openshift-cluster-csi-drivers                      azure-file-csi-driver-node-sg6bt                             0/3     Init:CrashLoopBackOff   19 (2m6s ago)    74m
      openshift-controller-manager                       controller-manager-78db88c776-c8xqp                          0/1     Pending                 0                77m
      
      $ oc logs -f azure-file-csi-driver-controller-7664dc5dd8-phhrj -c azure-inject-credentials         
      Error: workload identity method failed: AZURE_FEDERATED_TOKEN_FILE environment variable not found or empty

      Expected results:

      Cluster is normal

      Additional info:

      must-gather: https://drive.google.com/file/d/1G_wgMWyGgUzX-u6-dAaSPjJDzg65Yss1/view?usp=sharing

              rbednar@redhat.com Roman Bednar
              rhn-support-zhsun Zhaohua Sun
              None
              None
              Wei Duan Wei Duan
              None
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: