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

machine-api CO fails to start on the dualstack baremetal cluster

XMLWordPrintable

    • Critical
    • None
    • Proposed
    • False
    • Hide

      None

      Show
      None

      Description of problem:

          machine-api CO fails to start on the baremetal cluster:
      
      oc get co machine-api
      NAME          VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
      machine-api             False       True          True       135m    Operator is initializing
      
      apiVersion: config.openshift.io/v1
      kind: ClusterOperator
      metadata:
        annotations:
          capability.openshift.io/name: MachineAPI
          exclude.release.openshift.io/internal-openshift-hosted: "true"
          include.release.openshift.io/self-managed-high-availability: "true"
          include.release.openshift.io/single-node-developer: "true"
        creationTimestamp: "2024-05-21T10:42:54Z"
        generation: 1
        name: machine-api
        ownerReferences:
        - apiVersion: config.openshift.io/v1
          controller: true
          kind: ClusterVersion
          name: version
          uid: 11e027a9-e1d7-476b-ab55-ce028a51b006
        resourceVersion: "12511"
        uid: 8671f8e4-f379-44b0-aa43-e3a76895525c
      spec: {}
      status:
        conditions:
        - lastTransitionTime: "2024-05-21T10:50:42Z"
          message: 'Progressing towards operator: 4.16.0-rc.2'
          reason: SyncingResources
          status: "True"
          type: Progressing
        - lastTransitionTime: "2024-05-21T10:53:49Z"
          message: 'Failed when progressing towards operator: 4.16.0-rc.2 because minimum
            worker replica count (2) not yet met: current running replicas 0, waiting for
            [ecore-vkxlb-worker-0-2bcfv ecore-vkxlb-worker-0-8fh2g ecore-vkxlb-worker-0-frjcw
            ecore-vkxlb-worker-0-lnqrh]'
          reason: SyncingFailed
          status: "True"
          type: Degraded
        - lastTransitionTime: "2024-05-21T10:50:42Z"
          message: Operator is initializing
          reason: Initializing
          status: "False"
          type: Available
        - lastTransitionTime: "2024-05-21T10:50:42Z"
          status: "True"
          type: Upgradeable
        extension: null
        relatedObjects:
        - group: ""
          name: openshift-machine-api
          resource: namespaces
        - group: machine.openshift.io
          name: ""
          namespace: openshift-machine-api
          resource: machines
        - group: machine.openshift.io
          name: ""
          namespace: openshift-machine-api
          resource: machinesets
        - group: machine.openshift.io
          name: ""
          namespace: openshift-machine-api
          resource: machinehealthchecks
        - group: rbac.authorization.k8s.io
          name: ""
          namespace: openshift-machine-api
          resource: roles
        - group: rbac.authorization.k8s.io
          name: machine-api-operator
          resource: clusterroles
        - group: rbac.authorization.k8s.io
          name: machine-api-controllers
          resource: clusterroles
        - group: metal3.io
          name: ""
          namespace: openshift-machine-api
          resource: baremetalhosts

       

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

          4.16.0-rc.2

      How reproducible:

          so far once

      Steps to Reproduce:

          1. Install baremetal SNO HUB cluster
          2. Install ACM/MCE version 2.11
          3. Install TALM, GitOps operators
          4. Start baremetal cluster deployment with GitOps ZTP workflow
          

      Actual results:

          Deployment is stuck:
      
      oc get clusterdeployments.hive.openshift.io -n ecore
      NAME    INFRAID   PLATFORM          REGION   VERSION   CLUSTERTYPE   PROVISIONSTATUS   POWERSTATE   AGE
      ecore             agent-baremetal                                    Provisioning                   164m

      Expected results:

          machine-api operator is started on the spoke cluster

      Additional info:

          Dualstack baremetal setup

              rh-ee-tdomnesc Tudor Domnescu
              yprokule@redhat.com Yurii Prokulevych
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: