CORENET-6168: Add ovn tests extension#30560
Open
jluhrsen wants to merge 2 commits intoopenshift:mainfrom
Open
Conversation
|
Pipeline controller notification For optional jobs, comment This repository is configured in: automatic mode |
openshift-ci-robot
added
the
jira/valid-reference
|
@jluhrsen: This pull request references CORENET-4510 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 epic to target the "4.21.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-merge-robot
added
the
needs-rebase
jluhrsen
force-pushed
the
add-ovn-tests-extension
branch
from
21838fd to
2530736
Compare
openshift-merge-robot
removed
the
needs-rebase
Contributor
Author
|
/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.21-e2e-aws-ovn openshift/ovn-kubernetes#2889 |
Contributor
|
@jluhrsen: 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/2492bac0-cfed-11f0-8358-3266731cfe9a-0 |
5 tasks
openshift-merge-robot
added
the
needs-rebase
this is a no-op commit just to help visually search for test extension binaries Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
jluhrsen
force-pushed
the
add-ovn-tests-extension
branch
from
2530736 to
fb9c943
Compare
openshift-merge-robot
removed
the
needs-rebase
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: jluhrsen 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 |
|
Scheduling required tests: |
Contributor
Author
|
/payload-job periodic-ci-openshift-release-master-ci-4.21-e2e-aws-ovn-techpreview |
Contributor
|
@jluhrsen: 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/d0cdddf0-f712-11f0-8a43-5b8e3f27cf5c-0 |
Contributor
Author
|
/payload-job periodic-ci-openshift-release-master-ci-4.21-upgrade-from-stable-4.20-e2e-aws-ovn-upgrade |
Contributor
|
@jluhrsen: 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/246df2b0-f713-11f0-9ef8-c66ab29ab6a4-0 |
Contributor
Author
|
/payload-job periodic-ci-openshift-release-master-ci-4.21-upgrade-from-stable-4.20-e2e-azure-ovn-upgrade |
Contributor
Author
|
/payload-job periodic-ci-openshift-release-master-ci-4.21-e2e-gcp-ovn-upgrade |
Contributor
Author
|
/payload-job periodic-ci-openshift-hypershift-release-4.21-periodics-e2e-aks |
Contributor
Author
|
/payload-job periodic-ci-openshift-hypershift-release-4.21-periodics-e2e-aws-ovn |
Contributor
|
@jluhrsen: 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/39259910-f713-11f0-8001-b3fa6dda7770-0 |
Contributor
Author
|
/payload-job periodic-ci-openshift-release-master-ci-4.21-e2e-aws-upgrade-ovn-single-node |
Contributor
|
@jluhrsen: 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/3a746030-f713-11f0-92e0-2b2b6bce50cd-0 |
Contributor
|
@jluhrsen: 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/957eef30-16bd-11f1-8ef6-8f3a336991c0-0 |
|
Job Failure Risk Analysis for sha: fb9c943
Risk analysis has seen new tests most likely introduced by this PR. New Test Risks for sha: fb9c943
New tests seen in this PR at sha: fb9c943
|
Contributor
Author
|
/payload-job-with-prs periodic-ci-openshift-release-main-ci-4.22-e2e-aws-ovn openshift/ovn-kubernetes#3011 openshift/multus-cni#280 #30820 |
Contributor
|
@jluhrsen: 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/03ce5310-174d-11f1-8109-f196366c640e-0 |
Member
This run has one informing ote test failing, but that is ok and doesn't block to merge this PR. |
Member
|
/test e2e-metal-ipi-ovn-ipv6 |
|
Risk analysis has seen new tests most likely introduced by this PR. New Test Risks for sha: fb9c943
New tests seen in this PR at sha: fb9c943
|
Contributor
Author
@pperiyasamy , we have to wait for the OVNK d/s merge to land first. that has the |
Member
ok @jluhrsen , how is that possible ? i see making u/s tests as |
sgoveas
pushed a commit
to sgoveas/origin
that referenced
this pull request
Mar 5, 2026
the following test cases are duplicated with test that will run with the ovnk OTE work which will be enabled with this PR [0]. they are failing because upstream OVNK has bumped it's CNI version to 1.1.0 and these tests are hardcoded here (or in multus [1]) and don't accept 1.1.0 yet. The upstream change in ovnk also updated it's tests so when they run via OTE, they will pass. [0] openshift#30560 [1] openshift/multus-cni#278 Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
Member
|
/test e2e-metal-ipi-ovn-ipv6 |
Contributor
Author
|
/payload 4.22 ci blocking |
Contributor
|
@jluhrsen: trigger 5 job(s) of type blocking for the ci release of OCP 4.22
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/e18ead40-18b4-11f1-80a8-ea43b9c61780-0 |
Contributor
Author
|
/retest all |
Contributor
Author
|
/test e2e-aws-csi /test e2e-aws-jenkins /test e2e-aws-ovn-fips /test e2e-aws-ovn-image-registry /test e2e-aws-ovn-microshift /test e2e-aws-ovn-microshift-serial /test e2e-aws-ovn-serial-1of2 /test e2e-aws-ovn-serial-2of2 /test e2e-gcp-csi /test e2e-gcp-ovn /test e2e-gcp-ovn-builds /test e2e-gcp-ovn-image-ecosystem /test e2e-gcp-ovn-upgrade /test e2e-metal-ipi-ovn-ipv6 /test e2e-vsphere-ovn /test e2e-vsphere-ovn-upi |
|
Risk analysis has seen new tests most likely introduced by this PR. New Test Risks for sha: fb9c943
New tests seen in this PR at sha: fb9c943
|
|
Risk analysis has seen new tests most likely introduced by this PR. New Test Risks for sha: fb9c943
New tests seen in this PR at sha: fb9c943
|
|
Risk analysis has seen new tests most likely introduced by this PR. New Test Risks for sha: fb9c943
New tests seen in this PR at sha: fb9c943
|
Member
|
There is still two blocking jobs failing on the latest runs.
The tests expects stderr something like this:
but it got below:
it no longer includes |
Member
|
/retest |
Contributor
|
@jluhrsen: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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 kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
Risk analysis has seen new tests most likely introduced by this PR. New Test Risks for sha: fb9c943
New tests seen in this PR at sha: fb9c943
|
|
Risk analysis has seen new tests most likely introduced by this PR. New Test Risks for sha: fb9c943
New tests seen in this PR at sha: fb9c943
|
Member
@jluhrsen it failed again with same error, can you take a look ? |
Contributor
Author
@pperiyasamy, did some digging and I think we are now getting burned by the kube bump to 1.35. remember these tests were passing in that run from 3/3 but that was w/ k8s 1.34 and the new jobs are running with 1.35. looks like the way the So, two ways forward for now:
And, now all of this means that we have to get the current d/s merge in, then get #1 in, then see if we don't get burned YET AGAIN, by something else external. |
Contributor
fail as informing is the way to go for now... |
Contributor
Author
@tssurya , please get the d/s merge in, then we need to get the |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.