Uploaded image for project: 'MicroShift'
  1. MicroShift
  2. USHIFT-6075

Add global MicroShift configuration to releases testing scenarios

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • QE
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False
    • 3
    • None
    • None
    • uShift Sprint 277, uShift Sprint 278, uShift Sprint 279, uShift Sprint 280

      In QE Jenkins release testing, we use to run standard RF test suites with these configurations applied. Sometimes we set a few of them at the same time. These are very useful tests to validate these configurations don't interfere with each other.

      • FIPS: enabled and disabled
      • IP version: ipv4, ipv6, ipv6dualstack
      • low-latency: enabled and disabled
      • TLS protocol: v1.2 and v1.3
      • LVMS: enabled and disabled

      Analysis what scenarios need to added or modified to make this possible.

          There are no Sub-Tasks for this issue.

              knarra@redhat.com Rama Kasturi Narra
              agullon Alejandro Gullón
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: