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

Cluster install failed on ASH

    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • Proposed
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      Cluster install failed on ASH, such as job https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_cloud-provider-azure/155/pull-ci-openshift-cloud-provider-azure-main-e2e-azurestack-ipi/2030221110649294848

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

      4.22

      How reproducible:

      Always 

      Steps to Reproduce:

          1. Create an ASH cluster
          2. Check cluster status
          3.
          

      Actual results:

      Cluster install failed 
      
      zhsun:ash/ $ oc logs -n openshift-ingress-operator deployment/ingress-operator -c ingress-operator --tail=100
      2026-03-09T10:32:45.809Z    ERROR    operator.init.controller-runtime.source.Kind    wait/loop.go:87    if kind is a CRD, it should be installed before calling Start    {"kind": "Route.route.openshift.io", "error": "failed to get restmapping: no matches for kind \"Route\" in version \"route.openshift.io/v1\""}
      
      zhsun:ash/ $ oc get co                                                                                                          [18:37:58]
      NAME                                       VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
      authentication                             4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   False       False         True       3h16m   APIServicesAvailable: PreconditionNotReady...
      baremetal                                  4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   True        False         False      3h16m
      cloud-controller-manager                   4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   True        False         False      3h23m
      cloud-credential                           4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   True        False         False      3h16m
      cluster-autoscaler                         4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   True        False         False      3h16m
      config-operator                            4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   True        False         False      3h17m
      console                                    4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   Unknown     False         False      3h16m
      control-plane-machine-set                  4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   True        False         False      3h13m
      csi-snapshot-controller                    4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   True        False         False      3h16m
      dns                                        4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   True        False         False      3h15m
      etcd                                       4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   True        False         False      3h15m
      image-registry
      ingress                                                                                           False       True          True       3h16m   The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.)
      insights                                   4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   True        False         False      3h17m
      kube-apiserver                             4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   True        False         False      3h9m
      kube-controller-manager                    4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   True        False         True       3h10m   GarbageCollectorDegraded: error fetching rules: Get "https://thanos-querier.openshift-monitoring.svc:9091/api/v1/rules": dial tcp 172.30.137.180:9091: connect: connection refused
      kube-scheduler                             4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   True        False         False      3h13m
      kube-storage-version-migrator              4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   True        False         False      3h17m
      machine-api                                4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   True        False         False      176m
      machine-approver                           4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   True        False         False      3h16m
      machine-config                             4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   True        False         False      3h18m
      marketplace                                4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   True        False         False      3h16m
      monitoring                                                                                        False       True          True       103m    UpdatingAlertmanager: reconciling Alertmanager Route failed: creating Route object failed: the server could not find the requested resource (post routes.route.openshift.io), UpdatingThanosQuerier: reconciling Thanos Querier Route failed: creating Route object failed: the server could not find the requested resource (post routes.route.openshift.io), UpdatingPrometheus: reconciling Prometheus API Route failed: creating Route object failed: the server could not find the requested resource (post routes.route.openshift.io), UpdatingPrometheus: Prometheus "openshift-monitoring/k8s": failed to get: prometheuses.monitoring.coreos.com "k8s" not found
      network                                    4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   True        False         False      3h20m
      node-tuning                                4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   True        False         False      128m
      olm                                        4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   True        False         False      3h15m
      openshift-apiserver                        4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   False       False         False      3h17m   APIServicesAvailable: PreconditionNotReady
      openshift-controller-manager               4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   True        False         False      3h6m
      openshift-samples
      operator-lifecycle-manager                 4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   True        False         False      3h16m
      operator-lifecycle-manager-catalog         4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   True        False         False      3h16m
      operator-lifecycle-manager-packageserver   4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   True        False         False      81m
      service-ca                                 4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   True        False         False      3h17m
      storage                                    4.22.0-0-2026-03-09-063227-test-ci-ln-yn3z9h2-latest   True        False         False      3h13m
      zhsun:ash/ $
      
      

      Expected results:

      Cluster install succeed on ASH

      Additional info:

          

              Unassigned Unassigned
              rhn-support-zhsun Zhaohua Sun
              Gaoyun Pei Gaoyun Pei
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: