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

prometheus rejects servicemonitor creation

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This is an LVMS Bug Report:

      Please create & attach a must-gather as indicated by this Guide to collect LVMS relevant data from the Cluster (linked to the latest version, use older versions of the documentation for older OCP releases as applicable

      Please make sure that you describe your storage configuration in detail. List all devices that you plan to work with for LVMS as well as any relevant machine configuration data to make it easier for an engineer to help out.

      Description of problem:

       after configuring lvm operator and creating lvmcluster I can see the following in prometheus controller logs:

level=warn ts=2024-11-20T10:33:20.264176948Z caller=resource_selector.go:126 component=prometheus-controller msg="skipping servicemonitor" error="it accesses file system via bearer token file which Prometheus specification prohibits" servicemonitor=openshift-storage/lvms-operator-metrics-monitor namespace=openshift-user-workload-monitoring prometheus=user-workload

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

       4.17.1

      Steps to Reproduce:

      Actual results:

      Expected results:

      lvm storage correctly monitored by prometheus

      Additional info:

              sakbas@redhat.com Suleyman Akbas
              lucamaf Luca Mattia Ferrari
              None
              None
              Minal Pradeep Makwana Minal Pradeep Makwana
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: