Skip to content

Conversation

@igsilya
Copy link
Contributor

@igsilya igsilya commented Jun 26, 2025

ovn-kubernetes container image moved to OVS 3.5 in: openshift/ovn-kubernetes#2593 as part of 4.19 to 4.18 sync: https://issues.redhat.com//browse/OCPBUGS-48710

We should keep OVS versions between microshift and ovn-k in sync.

ovn-kubernetes container image moved to this version in:
  openshift/ovn-kubernetes#2593

MicroShift should be kept in sync.

Signed-off-by: Ilya Maximets <i.maximets@ovn.org>
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Jun 26, 2025
@openshift-ci-robot
Copy link

@igsilya: This pull request references Jira Issue OCPBUGS-58139, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.z) matches configured target version for branch (4.18.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-48709 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-48709 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0, 4.19.z
  • bug has dependents

Requesting review from QA contact:
/cc @jogeo

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

Details

In response to this:

ovn-kubernetes container image moved to OVS 3.5 in: openshift/ovn-kubernetes#2593 as part of 4.19 to 4.18 sync: https://issues.redhat.com//browse/OCPBUGS-48710

We should keep OVS versions between microshift and ovn-k in sync.

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.

@igsilya
Copy link
Contributor Author

igsilya commented Jun 26, 2025

The test failure seems unrelated.
/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 26, 2025

@igsilya: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

@ggiguash
Copy link
Contributor

/lgtm
/approved
/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jun 27, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 27, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 27, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, igsilya

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

The pull request process is described here

Details 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 27, 2025
@ggiguash
Copy link
Contributor

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jun 27, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 29621e0 into openshift:release-4.18 Jun 27, 2025
10 checks passed
@openshift-ci-robot
Copy link

@igsilya: Jira Issue OCPBUGS-58139: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-58139 has been moved to the MODIFIED state.

Details

In response to this:

ovn-kubernetes container image moved to OVS 3.5 in: openshift/ovn-kubernetes#2593 as part of 4.19 to 4.18 sync: https://issues.redhat.com//browse/OCPBUGS-48710

We should keep OVS versions between microshift and ovn-k in sync.

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

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants