Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-23737

The template for metrics.yaml for CloudKitty is wrong in telemetry-operator

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • rhos-18.0.16
    • rhos-18.0.15
    • openstack-cloudkitty
    • None
    • Bug Delivery Tracker
    • 1
    • Important

      To Reproduce Steps to reproduce the behavior:

      1. Enable and configure CloudKitty to get ratings
      2. openstack rating dataframes get -> retrieves dataframes with empty id and user_id

      Expected behavior

      • id and user_id fields do not exist in our environment, they should be configured as resource and user

      Bug impact

      • The impact is that the processor can only calculate dataframes for one resource even if there are multiples, as there is no way to tell them apart

      Known workaround

      • Stop the telemetry operator to avoid it overwriting the configuration
      • Modify the metrics.yaml contents in the cloudkitty-config-data secret

              rhn-engineering-jlarriba Juan Larriba
              rhn-engineering-jlarriba Juan Larriba
              rhos-conplat-observability
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: