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

OSP18 Telemetry Operator update - Test

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • None
    • None
    • 5
    • CloudOps 2024 Sprint 17, CloudOps 2024 Sprint 19
    • 2

      Useful links:
      Email with tasks information
      Add updates pull request

      Update OSP operator process

      To be ready for GA we have at least do manual testing of updates.

      We have to test Telemetry Operator update and verify that after the update everything is working as expected.

      If we have an appropriate version of telemetry-operator in the repository, when the OO kills the previous version and runs the new TO version from the repo, the TO should independently be reconfiguring all the configmaps and secrets and trigger restarts of all the pods, which in turn will be downloading new versions of the service containers, as the download policy is Always. 

          1.
          		 Run Zuul Autoscaling job on hypervisor Sub-task Closed Major Alex Yefimov
          2.
          		 Deploy Logging on the Zuul Autoscaling hypervisor Sub-task Closed Major Alex Yefimov
          3.
          		 Add telemetry update job to the Cloudops component pipeline Sub-task Closed Undefined Alex Yefimov

              rhn-support-ayefimov Alex Yefimov
              lnatapov@redhat.com Leonid Natapov
              rhos-dfg-cloudops
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: