Uploaded image for project: 'Cluster Observability Operator'
  1. Cluster Observability Operator
  2. COO-195

CVP tests are failing for COO 0.3.0 release

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • 0.3.0
    • 0.2.0, 0.3.0
    • None
    • None
    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • MON Sprint 255
    • Critical
    • No

      In COO 0.3.0 errata CVP test are failing and complaining about

       bundle@sha256:f01a018c3c83dab43aee9d66fe2916aa3d14f3ad6c20dc4e8350fe0f18a08085]" error="Invalid bundle cluster-observability-operator.0.3.0, replaces nonexistent bundle cluster-observability-operator.0.2.0"
      Error: Invalid bundle cluster-observability-operator.0.3.0, replaces nonexistent bundle cluster-observability-operator.0.2.0
      Usage:

      In 4.16

      2024-06-19 16:18:31,168 iib.workers.api_utils ForkPoolWorker-1 request-751926 INFO api_utils.set_request_state Setting the state of request 751926 to "failed" with the reason "Failed to add the bundles to the index image: Invalid bundle cluster-observability-operator.0.3.0, replaces nonexistent bundle cluster-observability-operator.0.2.0"
      

      The reason for this is because 0.2.0 COO images doesn't exist in 4.16 release. There's a couple of tickets to CLOUDDST to fix this. Once this is done, the tests will just pass.

      https://issues.redhat.com/browse/CLOUDDST-23162
      https://issues.redhat.com/browse/CLOUDDST-23163

        1. image-2024-06-20-09-26-36-786.png
          20 kB
          Rayford Johnson
        2. image-2024-06-20-09-59-51-957.png
          32 kB
          Rayford Johnson
        3. image-2024-06-20-10-00-12-102.png
          6 kB
          Rayford Johnson

              dmellado1@redhat.com Daniel Mellado Area
              dmellado1@redhat.com Daniel Mellado Area
              Mario Fernandez Herrero, Rayford Johnson
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: