• Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • None
    • 3
    • False
    • None
    • False
    • OCPSTRAT-1389 - On Cluster Layering: Phase 3 (GA)
    • MCO Sprint 262, MCO Sprint 264
    • 0.000

      The original scope of this task is represented across this story & MCO-1494.

      With OCL GA'ing soon, we'll need a blocking path within our e2e test suite that must pass before a PR can be merged. This story represents the first stage in creating the blocking path:

      1. Migrate the tests from e2e-gcp-op-techpreview into a new test suite called e2e-ocl. This can be done by moving the tests in the MCO repo from the test/e2e-techpreview folder to a new test/e2e-ocl folder. There might be some minor cleanups such as fixing duplicate function names, etc. but it should be fairly straightforward to do.
      2. Make a new e2e-gcp-op-ocl job to call the newly created e2e-ocl test suite. This test should first be added as optional for 4.19 so it can be stability tested before it is made blocking for 4.18 & 4.19. This will require a PR to the openshift/release repo to call the new test for 4.19 & master. This should be a pretty straightforward config change.

            [MCO-1416] Separate OCL e2e tests into new test suite

            Closing this story as complete as this story will represent the initial phase for making OCL e2e tests blocking. Next steps include:

            1. Work through OCPBUGS-46421 to improve the stability of the OCL e2e test.
            2. Complete MCO-1494 to make the OCL tests blocking for 4.18 & 4.19.

            Isabella Janssen added a comment - Closing this story as complete as this story will represent the initial phase for making OCL e2e tests blocking. Next steps include: Work through OCPBUGS-46421 to improve the stability of the OCL e2e test. Complete MCO-1494 to make the OCL tests blocking for 4.18 & 4.19.

            Work Completed:

            • The OCL e2e tests were moved into their own test suite (PR)
            • With help from zzlotnik@redhat.com, some enhancements were made to the OCL e2e tests (PR)
            • A PR into the openshift/release repo created a new, optional, OCL e2e test suite for 4.19

            Work Todo:

            • See how OCL e2e tests preform on new PRs & make them more stable, as needed
            • Backport OCL e2e tests into 4.18 (MCO repo)
            • Create the OCL e2e test suite for 4.18 in openshift/release repo
            • Make OCL e2e tests blocking in openshift/release repo (4.18 & 4.19)

            Isabella Janssen added a comment - Work Completed: The OCL e2e tests were moved into their own test suite ( PR ) With help from zzlotnik@redhat.com , some enhancements were made to the OCL e2e tests ( PR ) A PR into the openshift/release repo created a new, optional, OCL e2e test suite for 4.19 Work Todo: See how OCL e2e tests preform on new PRs & make them more stable, as needed Backport OCL e2e tests into 4.18 (MCO repo) Create the OCL e2e test suite for 4.18 in openshift/release repo Make OCL e2e tests blocking in openshift/release repo (4.18 & 4.19)

            PRs for both repos are ready for review from a development perspective. However, I am waiting to open the MCO repo PR until Urvashi's PR (Use Jobs for OCL builds) lands so my PR can be rebased. The Openshift release PR should be merged after the MCO repo's PR.

            Isabella Janssen added a comment - PRs for both repos are ready for review from a development perspective. However, I am waiting to open the MCO repo PR until Urvashi's PR (Use Jobs for OCL builds) lands so my PR can be rebased. The Openshift release PR should be merged after the MCO repo's PR.

              rh-ee-ijanssen Isabella Janssen
              zzlotnik@redhat.com Zack Zlotnik
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: