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

UWM prometheus pods not starting due to variable not being defined.

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 5
    • Moderate
    • No
    • None
    • None
    • MON Sprint 245
    • 1
    • Done
    • Bug Fix
    • Hide
      * Previously, the `config-reloader` for Prometheus for user-defined projects would fail if unset environment variables were used in the `ServiceMonitor` configuration, which resulted in Prometheus pods failing. With this release, the reloader no longer fails when an unset environment variable is encountered. Instead, unset environment variables are left as they are, while set environment variables are expanded as usual. Any expansion errors, suppressed or otherwise, can be tracked through the `reloader_config_environment_variable_expansion_errors` variable. (link:https://issues.redhat.com/browse/OCPBUGS-23252[*OCPBUGS-23252*])
      Show
      * Previously, the `config-reloader` for Prometheus for user-defined projects would fail if unset environment variables were used in the `ServiceMonitor` configuration, which resulted in Prometheus pods failing. With this release, the reloader no longer fails when an unset environment variable is encountered. Instead, unset environment variables are left as they are, while set environment variables are expanded as usual. Any expansion errors, suppressed or otherwise, can be tracked through the `reloader_config_environment_variable_expansion_errors` variable. (link: https://issues.redhat.com/browse/OCPBUGS-23252 [* OCPBUGS-23252 *])
    • None
    • None
    • None
    • None

      Description of problem:

      UWM prometheus pods not starting due to variable not being defined

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

      All RHOCP 4 version

      How reproducible:

      Steps to Reproduce:

      1. Install a cluster 
2. Enable UserWorkload monitoring on the cluster
3. Define a service monitor as mentioned in the attached file

      Actual results:

      Prometheus pods under UWM fails to start due to unwanted variable

      Expected results:

      Pods to start correctly

      Additional info:h4. Description of problem:

      UWM prometheus pods not starting due to variable not being defined

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

      All RHOCP 4 version

      How reproducible:

      Steps to Reproduce:

      1. Install a cluster 
2. Enable UserWorkload monitoring on the cluster
3. Define a service monitor as mentioned in the attached file

      Actual results:

      Prometheus pods under UWM fails to start due to unwanted variable

      Expected results:

      Pods to start correctly

      Additional info:

              prasriva@redhat.com Pranshu Srivastava
              rhn-support-ssonigra Sonigra Saurab
              None
              Simon Pasquier
              Junqi Zhao Junqi Zhao
              Eliska Romanova Eliska Romanova
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: