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

Cannot use new proxy settings in Alertmanager configuration

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • 4.16.z
    • 4.15.z, 4.16.z
    • Monitoring
    • Moderate
    • None
    • MON Sprint 258
    • 1
    • False
    • Hide

      None

      Show
      None
    • NA
    • Release Note Not Required
    • In Progress

      This is a clone of issue OCPBUGS-38398. The following is the description of the original issue:

      This is a clone of issue OCPBUGS-38174. The following is the description of the original issue:

      Description of problem:

      The prometheus operator fails to reconcile when proxy settings like no_proxy are set in the Alertmanager configuration secret.    

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

      4.15.z and later    

      How reproducible:

          Always when AlertmanagerConfig is enabled

      Steps to Reproduce:

          1. Enable UWM with AlertmanagerConfig
          enableUserWorkload: true
          alertmanagerMain:
            enableUserAlertmanagerConfig: true
          2. Edit the "alertmanager.yaml" key in the alertmanager-main secret (see attached configuration file)
          3. Wait for a couple of minutes.
          

      Actual results:

      Monitoring ClusterOperator goes Degraded=True.
          

      Expected results:

      No error
          

      Additional info:

      The Prometheus operator logs show that it doesn't understand the proxy_from_environment field.
          

              spasquie@redhat.com Simon Pasquier
              openshift-crt-jira-prow OpenShift Prow Bot
              Junqi Zhao Junqi Zhao
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: