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-4762: [release-4.10] manifest: bump to openvswitch2.17 #1147

Merged
merged 1 commit into from Feb 22, 2023

Conversation

dcbw
Copy link
Contributor

@dcbw dcbw commented Feb 2, 2023

We need to consolidate OVS streams and move off OVS 2.16. Bump host OS OVS to 2.17 which has a good track record the past 10 months in 4.11+.

We need to consolidate OVS streams and move off OVS 2.16. Bump host OS
OVS to 2.17 which has a good track record the past 10 months in 4.11+.
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 2, 2023

@dcbw: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

manifest: bump to openvswitch2.17

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.

@dcbw dcbw changed the title manifest: bump to openvswitch2.17 [release-4.10] manifest: bump to openvswitch2.17 Feb 2, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 2, 2023

@dcbw: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

[release-4.10] manifest: bump to openvswitch2.17

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.

@dcbw dcbw changed the title [release-4.10] manifest: bump to openvswitch2.17 OCPBUGS-4762: [release-4.10] manifest: bump to openvswitch2.17 Feb 2, 2023
@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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Feb 2, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 2, 2023

@dcbw: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

OCPBUGS-4762: [release-4.10] manifest: bump to openvswitch2.17

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.

@openshift-ci-robot
Copy link

@dcbw: This pull request references Jira Issue OCPBUGS-4762, which is valid.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.10.z) matches configured target version for branch (4.10.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-4761 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
  • dependent Jira Issue OCPBUGS-4761 targets the "4.11.z" version, which is one of the valid target versions: 4.11.0, 4.11.z
  • bug has dependents

Requesting review from QA contact:
/cc @mffiedler

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

In response to this:

We need to consolidate OVS streams and move off OVS 2.16. Bump host OS OVS to 2.17 which has a good track record the past 10 months in 4.11+.

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.

@cgwalters
Copy link
Member

This is already happening as part of us switching to 9.2 for 4.13, so I think we can close this?

@cgwalters
Copy link
Member

See https://issues.redhat.com/browse/COS-1926 for the latest, but specifically here

# We need the published 9.0 openvswitch since it has s390x

(Incidentally...having openvswitch on the host has recently caused us a not-small amount of pain...moving it into a container would have significantly helped recent rhel9 work)

@cgwalters
Copy link
Member

Oh I see, you want to get this all the way back to 4.10? Then I guess it's indeed easiest to land in master now.
/approve

Note though this should really be tested somewhat manually pre-merge directly in a modified 4.10 build I think.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 2, 2023
@cgwalters
Copy link
Member

And now that I look sorry this is already directly against release-4.10...

From your PoV is this tested?

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 2, 2023

@dcbw: all tests passed!

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.

@ashcrow ashcrow requested review from cgwalters and removed request for jlebon February 2, 2023 21:58
@travier
Copy link
Member

travier commented Feb 3, 2023

/label cherry-pick-approved
/label backport-risk-assessed
Waiting on confirmation before we LGTM this one.

@openshift-ci openshift-ci bot added cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. labels Feb 3, 2023
@sdodson
Copy link
Member

sdodson commented Feb 15, 2023

@dcbw I think they're just waiting on your confirmation that this has been tested in 4.10.

@travier
Copy link
Member

travier commented Feb 21, 2023

@dcbw As Scott said, waiting on confirmation that you think this is ready and we'll merge it.

Copy link

@flavio-fernandes flavio-fernandes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@abhat
Copy link

abhat commented Feb 22, 2023

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 22, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 22, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhat, cgwalters, dcbw, flavio-fernandes

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

The pull request process is described 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

@openshift-merge-robot openshift-merge-robot merged commit 1c74706 into openshift:release-4.10 Feb 22, 2023
@openshift-ci-robot
Copy link

@dcbw: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

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

In response to this:

We need to consolidate OVS streams and move off OVS 2.16. Bump host OS OVS to 2.17 which has a good track record the past 10 months in 4.11+.

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.

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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. 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.

None yet

8 participants