NE-2292: Add Gateway API OLM to NO-OLM migration upgrade test#30897
NE-2292: Add Gateway API OLM to NO-OLM migration upgrade test#30897gcs278 wants to merge 2 commits intoopenshift:mainfrom
Conversation
|
Pipeline controller notification For optional jobs, comment This repository is configured in: automatic mode |
openshift-ci-robot
added
the
jira/valid-reference
|
@gcs278: This pull request references NE-2292 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci
bot
added
the
do-not-merge/work-in-progress
|
Skipping CI for Draft Pull Request. |
|
Important Review skippedAuto reviews are limited based on label configuration. 🚫 Excluded labels (none allowed) (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
openshift-ci
bot
added
the
approved
|
/test e2e-gcp-ovn-upgrade |
|
/test ? |
gcs278
force-pushed
the
gwapi-olm-upgrade-test
branch
from
90dbe8d to
ac9d301
Compare
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: gcs278 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
openshift-ci
bot
removed
the
approved
|
/test e2e-gcp-ovn-upgrade |
gcs278
force-pushed
the
gwapi-olm-upgrade-test
branch
2 times, most recently
from
b08e876 to
4df0775
Compare
|
/test e2e-gcp-ovn-upgrade |
|
Risk analysis has seen new tests most likely introduced by this PR. New Test Risks for sha: 4df0775
New tests seen in this PR at sha: 4df0775
|
|
/test ? |
|
/payload list |
|
/payload-job periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade |
|
@gcs278: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/60c65dd0-22f9-11f1-91b0-a3e2ef55f2e7-0 |
|
Ah darn this isn't going to work because |
|
@gcs278: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/c6220410-2306-11f1-9c3a-90af7c7cc380-0 |
gcs278
force-pushed
the
gwapi-olm-upgrade-test
branch
from
4df0775 to
5b67673
Compare
|
[trying again] Okay, this is a bit crazy, but I created a draft promotion PR (openshift/api#2772) so that we can test with NoOLM as default since we don't have /payload-job-with-prs periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade openshift/api#2772 openshift/cluster-ingress-operator#1354 Additionally, this should still run for OLM to OLM, or noOLM to noOLM (it's a generic z stream upgrade test): This would be noOLM to noOLM: So there's our 3 cases:
|
|
@gcs278: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/23e6af60-2307-11f1-992d-12ede9d2e079-0 |
|
@gcs278: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/26a088fc-2307-11f1-9da4-6bca82f01e76-0 |
|
Job Failure Risk Analysis for sha: e6d2507
Risk analysis has seen new tests most likely introduced by this PR. New tests seen in this PR at sha: e6d2507
|
|
So close, but it appears that the cluster-role was not applied when I used my promotion PR to effectively bypass not having a techpreview upgrade-from-stable job to test with. This made me realize we must of forgotten to remove these tags when we promote to GA: openshift/cluster-ingress-operator#1393. Now that openshift/cluster-ingress-operator#1354 is now merged, we can also drop that from this command. /payload-job-with-prs periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade openshift/api#2772 openshift/cluster-ingress-operator#1393 |
|
@gcs278: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0ab81910-23c6-11f1-8635-bf728c1f5aad-0 |
|
the upgrade test here (OLM to OLM) succeeded, but failed on something else, but I'll re-test anyways: /test e2e-gcp-ovn-upgrade |
|
Essentially this run was successful. It failed because pod we used for HttpRoute testing doesn't survive an upgrade. We need to use a deployment so pods can recreate. Otherwise, successful migration E2E test run. /payload-job-with-prs periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade openshift/api#2772 openshift/cluster-ingress-operator#1393 |
|
/test e2e-gcp-ovn-upgrade |
|
@gcs278: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/1e4a3720-2406-11f1-93e5-9f16732fd0e5-0 |
|
Job Failure Risk Analysis for sha: 522231d
Risk analysis has seen new tests most likely introduced by this PR. New tests seen in this PR at sha: 522231d
|
gcs278
force-pushed
the
gwapi-olm-upgrade-test
branch
2 times, most recently
from
f780e33 to
1a39020
Compare
|
The last run was a upgrade success! but the tests failed because #30905 wasn't merged yet - now it is. I did a clean up, and this is nearly ready for review, but let's keep running: OLM to noOLM OLM to OLM noOLM to noOLM (idk why this won't trigger) |
|
@gcs278: An error was encountered. No known errors were detected, please see the full error message for details. Full error message.
unable to get additional pr info from string: OLM: string: OLM doesn't match expected format: org/repo#number
Please contact an administrator to resolve this issue. |
|
/payload-job-with-prs periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade openshift/api#2772 openshift/cluster-ingress-operator#1393 |
|
@gcs278: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0ddd5ec0-2493-11f1-8cf8-effe9a495bea-0 |
|
/test e2e-gcp-ovn-upgrade |
|
/testwith openshift/origin/main/e2e-gcp-ovn-upgrade openshift/api#2772 openshift/cluster-ingress-operator#1393 |
gcs278
force-pushed
the
gwapi-olm-upgrade-test
branch
from
1a39020 to
2c98e57
Compare
|
/test e2e-gcp-ovn-upgrade |
|
Last payload nearly worked, but i make a mistake assuming CSV, Subscription shouldn't be there after the install. Also, i needed to clean up CSV for tests that run after. This should be it: /payload-job-with-prs periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade openshift/api#2772 openshift/cluster-ingress-operator#1393 |
|
@gcs278: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/69a77f80-24c8-11f1-9403-ad1a7c99fb97-0 |
Add upgrade test validating Gateway API migration from OLM-based Istio to CIO-managed Sail Library during 4.21 to 4.22 upgrades. Setup creates Gateway/HTTPRoute with OLM provisioning and tests connectivity. Test validates migration: Gateway remains programmed, Istiod running, Istio CRDs stay OLM-managed, GatewayClass has CIO finalizer, Istio CR deleted, subscription persists. Teardown cleans up all resources.
Previously, HttpRoute test used a pod, but a pod won't survive a reboot during the upgrade process.
gcs278
force-pushed
the
gwapi-olm-upgrade-test
branch
from
2c98e57 to
3b1447c
Compare
|
/payload-abort |
|
/payload-job-with-prs periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade openshift/api#2772 openshift/cluster-ingress-operator#1393 |
|
@gcs278: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/8a761690-24c8-11f1-9c74-da2cb51d6692-0 |
|
/test e2e-gcp-ovn-upgrade |
|
/testwith openshift/origin/main/e2e-gcp-ovn-upgrade openshift/api#2772 openshift/cluster-ingress-operator#1393 |
2 participants
Add upgrade test validating Gateway API migration from OLM-based Istio to CIO-managed Sail Library during 4.21 to 4.22 upgrades.
Setup creates Gateway/HTTPRoute with OLM provisioning and tests connectivity. Test validates migration: Gateway remains programmed, Istiod running, Istio CRDs stay OLM-managed, GatewayClass has CIO finalizer, Istio CR deleted, subscription persists. Teardown cleans up all resources.
CC: @rhamini3