OCPBUGS-44596: Mount OVS directory instead of socket file

[mkowalski]

When mounting the OVS DB socket directly as a file (/run/openvswitch/db.sock) instead of mounting the whole directory, handler container loses access to the OVS DB in case of OVS daemon restart on the host. This can only be fixed by restarting the container so that it mounts again the correct file.

To remediate this, we are mounting the whole /run/openvswitch directory so that DB connection can be gracefully restored by the handler itself.

Closes: OCPBUGS-44596

[openshift-ci-robot]

@mkowalski: This pull request references Jira Issue OCPBUGS-44596, which is invalid:

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

When mounting the OVS DB socket directly as a file (/run/openvswitch/db.sock) instead of mounting the whole directory, handler container loses access to the OVS DB in case of OVS daemon restart on the host. This can only be fixed by restarting the container so that it mounts again the correct file.

To remediate this, we are mounting the whole /run/openvswitch directory so that DB connection can be gracefully restored by the handler itself.

Closes: OCPBUGS-44596

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mkowalski

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

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

[mkowalski]

/jira refresh

[openshift-ci-robot]

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

Requesting review from QA contact:
/cc @rbbratta

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]

@mkowalski: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-handler-azure	e7e085c	link	false	/test e2e-handler-azure

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-sigs/prow repository. I understand the commands that are listed here.

[mkowalski]

/override ci/prow/security

[openshift-ci]

@mkowalski: Overrode contexts on behalf of mkowalski: ci/prow/security

In response to this:

/override ci/prow/security

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.

[mkowalski]

/test ci/prow/e2e-handler-azure

[openshift-ci]

@mkowalski: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test check-generate-bundle

/test e2e-handler-ovn-ipv4

/test e2e-operator-ovn-ipv4

/test images

/test security

/test unit

The following commands are available to trigger optional jobs:

/test e2e-handler-azure

Use /test all to run all jobs.

In response to this:

/test ci/prow/e2e-handler-azure

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.