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

doc link in PrometheusDataPersistenceNotConfigured message is 4.8

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • 4.12.0
    • Monitoring
    • None
    • Low
    • MON Sprint 228
    • 1
    • False
    • Hide

      None

      Show
      None
    • NA
    • Release Note Not Required
    • Set a Value

      Description of problem:

      4.12 cluster, no pv for prometheus, the doc still link to 4.8

      # oc get co monitoring -o jsonpath='{.status.conditions}' | jq 'map(select(.type=="Degraded"))'
      [
        {
          "lastTransitionTime": "2022-10-09T02:36:16Z",
          "message": "Prometheus is running without persistent storage which can lead to data loss during upgrades and cluster disruptions. Please refer to the official documentation to see how to configure storage for Prometheus: https://docs.openshift.com/container-platform/4.8/monitoring/configuring-the-monitoring-stack.html",
          "reason": "PrometheusDataPersistenceNotConfigured",
          "status": "False",
          "type": "Degraded"
        }
      ]

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

      4.12.0-0.nightly-2022-10-05-053337

      How reproducible:

      always

      Steps to Reproduce:

      1. no PVs for prometheus, check the monitoring operator status
      2.
      3.
      

      Actual results:

      the doc still link to 4.8

      Expected results:

      links to the latest doc

      Additional info:

      slack thread: 
      https://coreos.slack.com/archives/G79AW9Q7R/p1665283462123389

            sthaha@redhat.com Sunil Thaha
            juzhao@redhat.com Junqi Zhao
            Junqi Zhao Junqi Zhao
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: