OCPBUGS-37875: packages-openshift.yaml: bump OVS version to 3.4

[npinaeva]

ovn-k container counterpart: https://issues.redhat.com/browse/OCPBUGS-38270
previous bump: #1495

[openshift-ci-robot]

@npinaeva: This pull request references Jira Issue OCPBUGS-37875, which is invalid:

• expected the bug to target the "4.18.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.

Details

In response to this:

ovn-k container counterpart: https://issues.redhat.com/browse/OCPBUGS-38270

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.

[npinaeva]

/jira refresh

[openshift-ci-robot]

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

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.18.0) matches configured target version for branch (4.18.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @mike-nguyen

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.

[jlebon]

Based on the comments in the Jira ticket, it looks like this was tested already and no issues were encountered.

/lgtm
/approve

/hold

Feel free to unhold when ready.

[jlebon]

Not sure on the urgency on this, but unless this needs to land in the first 4.18 EC, let's hold it until the acknowledge-critical-fixes-only requirement is lifted.

[igsilya]

/lgtm

Just in case. Tested this version bump on a manually upgraded nightly and no issues observed. The observability functionality we're looking for with this upgrade also worked fine on a kernel/OVS level.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: igsilya, jlebon, npinaeva

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 [jlebon]

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

[npinaeva]

/hold cancel

[openshift-ci-robot]

@npinaeva: This pull request references Jira Issue OCPBUGS-37875. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.

Details

In response to this:

ovn-k container counterpart: https://issues.redhat.com/browse/OCPBUGS-38270
previous bump: #1495

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]

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

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.18.0) matches configured target version for branch (4.18.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @mike-nguyen

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

Details

In response to this:

ovn-k container counterpart: https://issues.redhat.com/browse/OCPBUGS-38270
previous bump: #1495

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.

[npinaeva]

closed by accident :'(

[npinaeva]

/cherry-pick release-4.17

[openshift-cherrypick-robot]

@npinaeva: once the present PR merges, I will cherry-pick it on top of release-4.17 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-4.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-sigs/prow repository.

[openshift-ci]

@npinaeva: 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.

[openshift-ci-robot]

@npinaeva: Jira Issue OCPBUGS-37875: All pull requests linked via external trackers have merged:

• openshift/os#1596

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

Details

In response to this:

ovn-k container counterpart: https://issues.redhat.com/browse/OCPBUGS-38270
previous bump: #1495

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-cherrypick-robot]

@npinaeva: new pull request created: #1597

Details

In response to this:

/cherry-pick release-4.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-sigs/prow repository.