Uploaded image for project: 'OCP Technical Release Team'
  1. OCP Technical Release Team
  2. TRT-1347

Disable Image Registry Disruption Monitoring When Not HA

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • None
    • False
    • None
    • False

      OCPBUGS-18596 and OCPBUGS-22382 track issues on metal and vsphere jobs with disruption for image registry. By default image registry is not enabled for these platforms but is enabled, in a non HA manor, for the tests. During discussion around the issue it was decided that unless / until these teams support HA deployments of image registry we should not be monitoring them for disruption.

      Devan floated the idea of checking to see if the image registry deployment set has replicas enabled and if not then selectively disable disruption monitoring.

            [TRT-1347] Disable Image Registry Disruption Monitoring When Not HA

            Devan Goodwin added a comment -

            Would it be better to disable with the new cli flags for disabling certain monitor tests? Can this be used to shut down just image registry today? Look for image-registry-availability monitor test.

            Doing it in origin though would help all jobs who may come along and forget to use this flag in their forked/separate CI steps.

            Devan Goodwin added a comment - Would it be better to disable with the new cli flags for disabling certain monitor tests? Can this be used to shut down just image registry today? Look for image-registry-availability monitor test. Doing it in origin though would help all jobs who may come along and forget to use this flag in their forked/separate CI steps.

              stbenjam Stephen Benjamin
              rh-ee-fbabcock Forrest Babcock
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: