Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-5769

Observability - metrics collector is failed to deploy on the local-cluster after y-upgrading to 2.8

XMLWordPrintable

    • Critical
    • Approved

      Description of problem: This env is for y-upgrading from 2.6.6 --> 2.7.4 --> 2.8.0 FC9, with running some automation testing, the observability metrics collector can't be deployed on the local-cluster now. The namespace open-cluster-management-addon-observability is always in terminating status, even though I have tried:

       - restart the observability operator

       - disable observability metrics collection in the MCOCR*

       - remove the namespace* open-cluster-management-addon-observability by this instruction

      But the metrics collector still failed to deploy on the local cluster.

      I don't think this issue is caused by the existing automation test case, we haven't met this issue and another FC9 fresh install env running these automation cases without this issue. Even though it's caused by automation cases, why manually disabling Observability and removing terminating namespace are not helpful? Is it caused by the cluster, but QE always uses this cluster for upgrading testing?

      There are other issues like even the metrics collectors are deployed on other managed clusters, but they are not listed on the Grafana dashboard, not sure if it's related to this issue.

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

      How reproducible:

      Steps to Reproduce:

      1. Upgrade ACM from 2.6.6 --> 2.7.4 --> 2.8.0 FC9
      2. Run Observability automation test cases
      3. metrics collector failed to deploy on the local-cluster

      Actual results:

      Expected results:

      Additional info:

            daliu@redhat.com DangPeng Liu
            cquredhat ChangLiang Qu
            ACM QE Team
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: