OCPBUGS-55316: [release-4.14] Upgrade openvswitch package version to 3.3

[igsilya]

Manual cherry-pick of #4700 due to some merge conflicts.

Open vSwitch 3.1 is EoL upstream and so the support of this version in FDP is limited. To ensure timely bug fix delivery for 4.14+ we need to upgrade to the current LTS stream, which is Open vSwitch 3.3. It will be fully supported for much longer.

This change follows a corresponding move of RHCOS at openshift/os#1794 and OVN-Kubernetes at openshift/ovn-kubernetes#2511 to the same OVS 3.3. MicroShift should stay in sync.

Corresponding os and ovn-kubernetes PRs above are already merged.

[igsilya]

/jira cherry-pick OCPBUGS-54714

[openshift-ci-robot]

@igsilya: Jira Issue OCPBUGS-54714 has been cloned as Jira Issue OCPBUGS-55316. Will retitle bug to link to clone.
/retitle OCPBUGS-55316: [release-4.14] Upgrade openvswitch package version to 3.3

Details

In response to this:

/jira cherry-pick OCPBUGS-54714

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]

@igsilya: This pull request references Jira Issue OCPBUGS-55316, which is invalid:

• expected dependent Jira Issue OCPBUGS-54714 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

Details

In response to this:

Manual cherry-pick of #4700 due to some merge conflicts.

Open vSwitch 3.1 is EoL upstream and so the support of this version in FDP is limited. To ensure timely bug fix delivery for 4.14+ we need to upgrade to the current LTS stream, which is Open vSwitch 3.3. It will be fully supported for much longer.

This change follows a corresponding move of RHCOS at openshift/os#1794 and OVN-Kubernetes at openshift/ovn-kubernetes#2511 to the same OVS 3.3. MicroShift should stay in sync.

Corresponding os and ovn-kubernetes PRs above are already merged.

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.

[ggiguash]

/lgtm

[openshift-ci]

[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:

• OWNERS [ggiguash]

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

[ggiguash]

/jira refresh

[openshift-ci-robot]

@ggiguash: This pull request references Jira Issue OCPBUGS-55316, which is invalid:

• expected dependent Jira Issue OCPBUGS-54714 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

Details

In response to this:

/jira refresh

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]

@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]

/label backport-risk-assessed
/label jira/valid-bug

[ggiguash]

/jira refresh

[openshift-ci-robot]

@ggiguash: This pull request references Jira Issue OCPBUGS-55316, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.14.z) matches configured target version for branch (4.14.z)
• bug is in the state POST, 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-54714 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-54714 targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.z
• bug has dependents

Requesting review from QA contact:
/cc @jogeo

Details

In response to this:

/jira refresh

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.

[kasturinarra]

/label cherry-pick-approved

[openshift-ci]

@kasturinarra: Can not set label cherry-pick-approved: Must be member in one of these teams: []

Details

In response to this:

/label cherry-pick-approved

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.

[pacevedom]

/label cherry-pick-approved

[openshift-ci-robot]

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

• openshift/microshift#4834

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

Details

In response to this:

Manual cherry-pick of #4700 due to some merge conflicts.

Open vSwitch 3.1 is EoL upstream and so the support of this version in FDP is limited. To ensure timely bug fix delivery for 4.14+ we need to upgrade to the current LTS stream, which is Open vSwitch 3.3. It will be fully supported for much longer.

This change follows a corresponding move of RHCOS at openshift/os#1794 and OVN-Kubernetes at openshift/ovn-kubernetes#2511 to the same OVS 3.3. MicroShift should stay in sync.

Corresponding os and ovn-kubernetes PRs above are already merged.

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.