Skip to content

[release-4.12] OCPBUGS-54618: bump ovnver to prevent CVE-2025-0650 being flagged #2542

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

Open
wants to merge 1 commit into
base: release-4.12
Choose a base branch
from

Conversation

jluhrsen
Copy link
Contributor

@jluhrsen jluhrsen commented May 5, 2025

Dockerfile.base had 23.06.1-112.el8fdp but according to this Security Advisory [0], it was resolved in 23.06-23.06.4-26

also, Dockerfile.fedora in dist/images/ was using and 22.06.0-33 and this Security Advisory [1] shows that it was resolved in 22.06-22.06.0-273

[0] https://access.redhat.com/errata/RHSA-2025:1094
[1] https://access.redhat.com/errata/RHSA-2025:1090

📑 Description

Fixes #

Additional Information for reviewers

✅ Checks

  • My code requires changes to the documentation
  • if so, I have updated the documentation as required
  • My code requires tests
  • if so, I have added and/or updated the tests as required
  • All the tests have passed in the CI

How to verify it

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 5, 2025
@openshift-ci-robot
Copy link
Contributor

@jluhrsen: This pull request references Jira Issue OCPBUGS-54618, which is invalid:

  • expected the bug to target either version "4.12." or "openshift-4.12.", but it targets "4.15.z" instead
  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-54618 to depend on a bug targeting a version in 4.13.0, 4.13.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

Dockerfile.base had 23.06.1-112.el8fdp but according to this Security Advisory [0], it was resolved in 23.06-23.06.4-26

also, Dockerfile.fedora in dist/images/ was using and 22.06.0-33 and this Security Advisory [1] shows that it was resolved in 22.06-22.06.0-273

[0] https://access.redhat.com/errata/RHSA-2025:1094
[1] https://access.redhat.com/errata/RHSA-2025:1090

📑 Description

Fixes #

Additional Information for reviewers

✅ Checks

  • My code requires changes to the documentation
  • if so, I have updated the documentation as required
  • My code requires tests
  • if so, I have added and/or updated the tests as required
  • All the tests have passed in the CI

How to verify it

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-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label May 5, 2025
@openshift-ci openshift-ci bot requested review from trozet and tssurya May 5, 2025 21:49
Copy link
Contributor

openshift-ci bot commented May 5, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jluhrsen
Once this PR has been reviewed and has the lgtm label, please assign tssurya for approval. For more information see the 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

@jluhrsen jluhrsen force-pushed the CVE-2025-0650-release-4.12 branch from 80be5d6 to 44d5dfe Compare May 5, 2025 22:01
Dockerfile.base had 23.06.1-112.el8fdp but according to this
Security Advisory [0], it was resolved in 23.06.4-26

also, Dockerfile.fedora in dist/images/ was using and
22.06.0-33 and this Security Advisory [1] shows that it was
resolved in 22.06.0-273

[0] https://access.redhat.com/errata/RHSA-2025:1094
[1] https://access.redhat.com/errata/RHSA-2025:1090

Signed-off-by: Jamo Luhrsen <[email protected]>
@jluhrsen jluhrsen force-pushed the CVE-2025-0650-release-4.12 branch from 44d5dfe to 5e45a95 Compare May 8, 2025 02:29
@jluhrsen jluhrsen changed the title OCPBUGS-54618: bump ovnver to prevent CVE-2025-0650 being flagged [release-4.12] OCPBUGS-54618: bump ovnver to prevent CVE-2025-0650 being flagged May 8, 2025
@jluhrsen
Copy link
Contributor Author

jluhrsen commented May 8, 2025

/retest

2 similar comments
@jluhrsen
Copy link
Contributor Author

jluhrsen commented May 8, 2025

/retest

@jluhrsen
Copy link
Contributor Author

/retest

Copy link
Contributor

openshift-ci bot commented May 12, 2025

@jluhrsen: 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/e2e-aws-ovn-hypershift 5e45a95 link false /test e2e-aws-ovn-hypershift
ci/prow/security 5e45a95 link false /test security
ci/prow/4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade 5e45a95 link true /test 4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade
ci/prow/4.12-upgrade-from-stable-4.11-local-gateway-e2e-aws-ovn-upgrade 5e45a95 link true /test 4.12-upgrade-from-stable-4.11-local-gateway-e2e-aws-ovn-upgrade

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-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira/invalid-bug Indicates that a referenced Jira bug is invalid 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.

2 participants