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

[IBMCloud] [CAPI] install private cluster with CAPI failed

XMLWordPrintable

    • No
    • Approved
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      install private cluster with CAPI failed by MissingNodeRef 

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

      4.19.0-0.nightly-2024-12-13-083421     

      How reproducible:

      Always    

      Steps to Reproduce:

      1.install private cluster based on bastion host
      2.prepare the install-config.yaml:
      publish: Internal
      featureSet: CustomNoUpgrade
      featureGates: ["ClusterAPIInstall=true"]
      baseDomain: private-ibmcloud-2.qe.devcluster.openshift.com
      credentialsMode: Manual
      platform:
        ibmcloud:
          region: jp-tok
          networkResourceGroupName: ci-op-0yrhzx7l-ac1a3-rg
          vpcName: ci-op-0yrhzx7l-ac1a3-vpc
          controlPlaneSubnets:
          - ci-op-0yrhzx7l-ac1a3-control-plane-jp-tok-3-0
          - ci-op-0yrhzx7l-ac1a3-control-plane-jp-tok-2-0
          - ci-op-0yrhzx7l-ac1a3-control-plane-jp-tok-1-0
          computeSubnets:
          - ci-op-0yrhzx7l-ac1a3-compute-jp-tok-3-0
          - ci-op-0yrhzx7l-ac1a3-compute-jp-tok-2-0
          - ci-op-0yrhzx7l-ac1a3-compute-jp-tok-1-0
          resourceGroupName: ci-op-0yrhzx7l-ac1a3-rg
      controlPlane:
        name: master
        platform:
          ibmcloud:
            type: bx2-4x16
            zones: [jp-tok-1, jp-tok-2, jp-tok-3]
        replicas: 3
      compute:
      - name: worker
        platform:
          ibmcloud:
            type: bx2-4x16
            zones: [jp-tok-1, jp-tok-2, jp-tok-3]
        replicas: 3
      proxy:
        httpProxy: http://XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX@10.244.128.4:3128
        httpsProxy: http://XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX@10.244.128.4:3128
      networking:
        machineNetwork:
        - cidr: 10.244.0.0/16
       3. install cluster failed
          

      Actual results:

      install failed 
      in bootkube.json of log-bundle
          "stage": "resolve-api-url",
          "phase": "stage end",
          "result": "failure",
          "errorLine": "76 resolve_url /usr/local/bin/bootstrap-verify-api-server-urls.sh",
          "errorMessage": "Checking if api.maxu-capi9p.private-ibmcloud.qe.devcluster.openshift.com of type API_URL is resolvable\nStarting stage resolve-api-url\nUnable to resolve API_URL api.maxu-capi9p.private-ibmcloud.qe.devcluster.openshift.com"
      
      in Cluster-openshift-cluster-api-guests-ci-op-0yrhzx7l-ac1a3-2vc6j.yaml
        - type: ControlPlaneInitialized
          status: "False"
          severity: Info
          lasttransitiontime: "2024-12-17T09:39:31Z"
          reason: MissingNodeRef
          message: Waiting for the first control plane machine to have its status.nodeRef
            set   

      Expected results:

      install succeed.   

      Additional info:

      install External cluster with proxy succeed.
      
      install Internal cluster failed, ref Prow Job: https://qe-private-deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gs/qe-private-deck/pr-logs/pull/openshift_release/59392/rehearse-59392-periodic-ci-openshift-verification-tests-master-installer-rehearse-4.19-installer-rehearse-ibmcloud-proxy-private-capi/1868948420899639296  
      https://qe-private-deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gs/qe-private-deck/pr-logs/pull/openshift_release/59392/rehearse-59392-periodic-ci-openshift-verification-tests-master-installer-rehearse-4.19-cucushift-installer-rehearse-ibmcloud-ipi-private-capi/1871051791659962368  

              cschaefe@redhat.com Christopher Schaefer
              maxu@redhat.com May Xu
              May Xu May Xu
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: