Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCPBUGS-26023: Dockerfile: Bump OVN to ovn-23.09.0-100.el9fdp #2016

Closed

Conversation

dceara
Copy link
Contributor

@dceara dceara commented Jan 12, 2024

Includes the following relevant change:

  • Make sure affinity learnt flows are auto deleted.
    [https://issues.redhat.com/browse/OCPBUGS-26023]
    [https://issues.redhat.com/browse/FDP-257]

Includes the following relevant change:
- Make sure affinity learnt flows are auto deleted.
  [https://issues.redhat.com/browse/OCPBUGS-26023]
  [https://issues.redhat.com/browse/FDP-257]

Signed-off-by: Dumitru Ceara <dceara@redhat.com>
@dceara dceara requested a review from dcbw as a code owner January 12, 2024 13:48
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 12, 2024
@openshift-ci-robot
Copy link
Contributor

@dceara: This pull request references Jira Issue OCPBUGS-26023, which is invalid:

  • expected the bug to target the "4.16.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Includes the following relevant change:

  • Make sure affinity learnt flows are auto deleted.
    [https://issues.redhat.com/browse/OCPBUGS-26023]
    [https://issues.redhat.com/browse/FDP-257]

- What this PR does and why is it needed

- Special notes for reviewers

- How to verify it

- Description for the changelog

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.

@dceara
Copy link
Contributor Author

dceara commented Jan 12, 2024

/hold

Waiting for green light from upstream ovn-org/ovn-kubernetes#4088.

And also for rpm mirrors to sync.

@trozet @npinaeva

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 12, 2024
Copy link
Contributor

openshift-ci bot commented Jan 12, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dceara
Once this PR has been reviewed and has the lgtm label, please assign abhat for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@dceara
Copy link
Contributor Author

dceara commented Jan 12, 2024

/test images

6 similar comments
@dceara
Copy link
Contributor Author

dceara commented Jan 12, 2024

/test images

@dceara
Copy link
Contributor Author

dceara commented Jan 15, 2024

/test images

@dceara
Copy link
Contributor Author

dceara commented Jan 15, 2024

/test images

@dceara
Copy link
Contributor Author

dceara commented Jan 15, 2024

/test images

@dceara
Copy link
Contributor Author

dceara commented Jan 16, 2024

/test images

@dceara
Copy link
Contributor Author

dceara commented Jan 16, 2024

/test images

@dceara
Copy link
Contributor Author

dceara commented Jan 16, 2024

/retest

@dceara
Copy link
Contributor Author

dceara commented Jan 17, 2024

/retest

ci/prow/okd-e2e-gcp-ovn fails in similar ways with other PRs, likely unrelated.

ci/prow/e2e-aws-ovn-windows - Contained sensitive information -- content removed. I'm not sure what to make of this; I think the cluster bringup failed.

ci/prow/e2e-vsphere-ovn:


tar: ./6650517f9707ca92ba6404efae69667c25bae8ff87efe7e1aa96968f542ad84c/audit_logs/kube-apiserver/ci-op-6yxxsw22-fb62e-4x96m-master-0-audit-2024-01-16T23-08-18.475.log.gz: file changed as we read it
tar: ./6650517f9707ca92ba6404efae69667c25bae8ff87efe7e1aa96968f542ad84c/audit_logs/kube-apiserver: file changed as we read it
tar: ./6650517f9707ca92ba6404efae69667c25bae8ff87efe7e1aa96968f542ad84c/audit_logs: file changed as we read it
tar: ./6650517f9707ca92ba6404efae69667c25bae8ff87efe7e1aa96968f542ad84c: file changed as we read it
tar: .: file changed as we read it
{"component":"entrypoint","error":"wrapped process failed: exit status 1","file":"k8s.io/test-infra/prow/entrypoint/run.go:84","func":"k8s.io/test-infra/prow/entrypoint.Options.internalRun","level":"error","msg":"Error executing test process","severity":"error","time":"2024-01-16T23:33:52Z"}
error: failed to execute wrapped command: exit status 1
}

happens at must gather time, probably a flake

ci/prow/4.16-upgrade-from-stable-4.15-local-gateway-e2e-aws-ovn-upgrade:

response Body: {"ProwJobName":"pull-ci-openshift-ovn-kubernetes-master-4.16-upgrade-from-stable-4.15-local-gateway-e2e-aws-ovn-upgrade","ProwJobRunID":1747360164849127424,"Release":"Presubmits","CompareRelease":"4.16","Tests":[{"Name":"[sig-node][invariant] alert/TargetDown should not be at or above info in ns/kube-system","Risk":{"Level":{"Name":"High","Level":100},"Reasons":["This test has passed 99.68% of 928 runs on jobs ['periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade'] in the last 14 days."]},"OpenBugs":[]}],"OverallRisk":{"Level":{"Name":"High","Level":100},"Reasons":["Maximum failed test risk: High"]},"OpenBugs":[]}

Looks unrelated.

ci/prow/e2e-aws-ovn-kubevirt:

error: failed to create/update secret: failed to update secret: Timeout: request did not complete within requested timeout - context deadline exceeded 

Unrelated.

@npinaeva
Copy link
Member

Included to #2018

Copy link
Contributor

openshift-ci bot commented Jan 17, 2024

@dceara: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/okd-e2e-gcp-ovn b3e0f9d link false /test okd-e2e-gcp-ovn
ci/prow/security b3e0f9d link false /test security

Full PR test history. Your PR dashboard.

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 kubernetes/test-infra repository. I understand the commands that are listed here.

@dceara
Copy link
Contributor Author

dceara commented Jan 17, 2024

Closing in favor of #2018

@dceara dceara closed this Jan 17, 2024
@openshift-ci-robot
Copy link
Contributor

@dceara: This pull request references Jira Issue OCPBUGS-26023. The bug has been updated to no longer refer to the pull request using the external bug tracker.

In response to this:

Includes the following relevant change:

  • Make sure affinity learnt flows are auto deleted.
    [https://issues.redhat.com/browse/OCPBUGS-26023]
    [https://issues.redhat.com/browse/FDP-257]

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants