OCPBUGS-22366: Restart the openvswitch service on [re]install

[barbacbd]

Restart the openvswitch service when installed/upgraded if it exists. This should resolve network connectivity issues during upgrades.

[openshift-ci-robot]

@barbacbd: This pull request references Jira Issue OCPBUGS-22366, which is invalid:

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

In response to this:

Restart the openvswitch service when installed/upgraded if it exists. This should resolve network connectivity issues during upgrades.

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.

[barbacbd]

@gpei I noticed that the state of openvswitch is active (exited). This state can be observed before and after these changes so it is not introduced here. I don't think this is causing issues but systemd does not believe that there is a daemon to watch/monitor.

[barbacbd]

/jira refresh

[openshift-ci-robot]

@barbacbd: This pull request references Jira Issue OCPBUGS-22366, 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.16.0) matches configured target version for branch (4.16.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @gpei

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.

[barbacbd]

/test e2e-aws-workers-rhel8

[barbacbd]

It appears that the current version of kubernetes is 1.29 and crio is only 1.28 causing the failure.

[barbacbd]

/retest-required

[gpei]

It appears that the current version of kubernetes is 1.29 and crio is only 1.28 causing the failure.

Yes, we've created a Jira issue to ART team for this https://issues.redhat.com/browse/ART-8558

[patrickdillon]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: barbacbd, patrickdillon

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:

• OWNERS [barbacbd,patrickdillon]

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

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 8ea9a41 and 2 for PR HEAD e80be9d in total

[barbacbd]

/retest-required

[barbacbd]

/retest-required

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD d96c87d and 1 for PR HEAD e80be9d in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD c369981 and 0 for PR HEAD e80be9d in total

[openshift-ci-robot]

/hold

Revision e80be9d was retested 3 times: holding

[sadasu]

/retest-required

[barbacbd]

/label acknowledge-critical-fixes-only

[gpei]

/test e2e-aws-workers-rhel8

[barbacbd]

/hold cancel

[openshift-ci]

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

[openshift-ci-robot]

@barbacbd: Jira Issue OCPBUGS-22366: All pull requests linked via external trackers have merged:

• openshift/openshift-ansible#12476

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

In response to this:

Restart the openvswitch service when installed/upgraded if it exists. This should resolve network connectivity issues during upgrades.

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.

[gpei]

/cherry-pick release-4.15

[openshift-cherrypick-robot]

@gpei: new pull request created: #12502

In response to this:

/cherry-pick release-4.15

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.