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

capi-ibmcloud-controller-manager ContainerCreating shouldn't happen on IBMCloud

XMLWordPrintable

    • Low
    • No
    • CLOUD Sprint 248
    • 1
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, the Cluster API {ibm-power-server-title} controller pod would start on the unsupported {ibm-cloud-title} platform.
      This caused the controller pod to get stuck in the creation phase.
      With this release, the cluster detects the difference between {ibm-power-server-title} and {ibm-cloud-title} and only starts on the supported platform.
      (link:https://issues.redhat.com/browse/OCPBUGS-28539[*OCPBUGS-28539*])
      Show
      * Previously, the Cluster API {ibm-power-server-title} controller pod would start on the unsupported {ibm-cloud-title} platform. This caused the controller pod to get stuck in the creation phase. With this release, the cluster detects the difference between {ibm-power-server-title} and {ibm-cloud-title} and only starts on the supported platform. (link: https://issues.redhat.com/browse/OCPBUGS-28539 [* OCPBUGS-28539 *])
    • Bug Fix
    • Done

      Description of problem:

      Pod capi-ibmcloud-controller-manager stuck in ContainerCreating on IBM cloud
      
      

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

          

      How reproducible:

      Always    

      Steps to Reproduce:

          1. Built a cluster on ibm cloud and enable TechPreviewNoUpgrade
          2.
          3.
          

      Actual results:

      4.16 cluster
      $ oc get po                        
      NAME                                                READY   STATUS              RESTARTS      AGE
      capi-controller-manager-6bccdc844-jsm4s             1/1     Running             9 (24m ago)   175m
      capi-ibmcloud-controller-manager-75d55bfd7d-6qfxh   0/2     ContainerCreating   0             175m
      cluster-capi-operator-768c6bd965-5tjl5              1/1     Running             0             3h
      
        Warning  FailedMount       5m15s (x87 over 166m)  kubelet            MountVolume.SetUp failed for volume "credentials" : secret "capi-ibmcloud-manager-bootstrap-credentials" not found
      
      $ oc get clusterversion               
      NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
      version   4.16.0-0.nightly-2024-01-21-154905   True        False         156m    Cluster version is 4.16.0-0.nightly-2024-01-21-154905
      
      4.15 cluster
      $ oc get po                           
      NAME                                                READY   STATUS              RESTARTS        AGE
      capi-controller-manager-6b67f7cff4-vxtpg            1/1     Running             6 (9m51s ago)   35m
      capi-ibmcloud-controller-manager-54887589c6-6plt2   0/2     ContainerCreating   0               35m
      cluster-capi-operator-7b7f48d898-9r6nn              1/1     Running             1 (17m ago)     39m
      $ oc get clusterversion           
      NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
      version   4.15.0-0.nightly-2024-01-22-160236   True        False         11m     Cluster version is 4.15.0-0.nightly-2024-01-22-160236        

      Expected results:

      No pod is in ContainerCreating status

      Additional info:

      must-gather: https://drive.google.com/file/d/1F5xUVtW-vGizAYgeys0V5MMjp03zkSEH/view?usp=sharing 

            ddonati@redhat.com Damiano Donati
            rhn-support-zhsun Zhaohua Sun
            Zhaohua Sun Zhaohua Sun
            Jeana Routh Jeana Routh
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: