Explicitly unmanage veth interfaces

[phoracek]

Is this a BUG FIX or a FEATURE ?:

/kind bug

What this PR does / why we need it:

nmstate 0.3 introduces a bug where all veths attached to nmstatectl
configured bridge turn into "managed" by NetworkManager. This was not
the case in 0.2.

Due to this regression, NetworkManager deliberatelly detaches veth
ifaces from the bridge and by doing that it disconnectecs Pods/VMs from
the network.

With this change, we explicitly set veth interfaces as unmanaged.

Important: With this change, it is no longer possible to change
configuration of bridges that have veths attached.

This should be reverted once https://bugzilla.redhat.com/show_bug.cgi?id=1932247 becomes available.

Special notes for your reviewer:

Release note:

Explicitly set host veths as unmanaged

[qinqon]

/lgtm
/approve

Ugly hack that will unblock upgrades, this will be removed after fix at nmstate.

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qinqon

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

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

[phoracek]

/cherry-pick release-0.37

[kubevirt-bot]

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

In response to this:

/cherry-pick release-0.37

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.

[phoracek]

/retest

[phoracek]

/override pull-kubernetes-nmstate-e2e-handler-k8s-future

[kubevirt-bot]

@phoracek: Overrode contexts on behalf of phoracek: pull-kubernetes-nmstate-e2e-handler-k8s-future

In response to this:

/override pull-kubernetes-nmstate-e2e-handler-k8s-future

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.

[kubevirt-bot]

@phoracek: new pull request created: #702

In response to this:

/cherry-pick release-0.37

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.

[kubevirt-bot]

@phoracek: The following test failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
pull-kubernetes-nmstate-e2e-handler-k8s-future	2e4da97	link	/test pull-kubernetes-nmstate-e2e-handler-k8s-future

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.