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

alarms-server fails to start with ACM 2.15 due to secret not existing

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • 4.20, 4.21
    • O-Cloud Manager Operator
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • Yes
    • None
    • Proposed
    • None
    • Done
    • Release Note Not Required
    • N/A
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-65758. The following is the description of the original issue:
      —
      Description of problem:

      Starting from ACM 2.15, it appears that the secret open-cluster-management-observability/observability-alertmanager-accessor-token does not get generated. There's a secret observability-alertmanager-accessor with a token field, but no certificates. The ACM docs recommend using the openshift-ingress/router-certs-default secret for certificates it seems.

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

      affects all o-cloud-manager versions, found with ACM pre-release build v2.15.0-213

      How reproducible:

      100%

      Steps to Reproduce:

          1. Deploy cluster with ACM 2.15 and enable observability, install o-cloud-manager operator
    2. Notice alarms server enter CrashLoopBackoff
    3.

      Actual results:

          alarms server CrashLoopBackoff

      Expected results:

          no CrashLoopBackoff

      Additional info:

      ACM docs

      google drive with alarms server logs

              dpenney1@redhat.com Don Penney
              rh-ee-klaskosk Kirsten Laskoski
              None
              None
              Kirsten Laskoski Kirsten Laskoski
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: