DPDK: Avoid overriding driver again during next os-net-config run

[Saravanan KR]

The problem is found in newton for the mellanox nics with DPDK, when os-net-config runs again. The behaviour of how os-net-config runs is different in newton from other versions. But it will run again during update/upgrade/ffu. So it is applicable to all version.

Intel nics will not be visible to user, when DPDK driver (vfio-pci) is bound to it, but mellnaox interfaces has a different behaviour, the interfaces is still visible to the user. And in certain versions of nic, it is not required to bind the interface at all, as the same driver is already used by the interface, for example Connect-X5 uses mlx5_core, which is required to for DPDK too.

Running driverctl again (for subsequent os-net-config runs) for the same dirver, results in connectivity loss on vxlan tunnels. And it requires ovs to be restarted restore it back.

Avoid driverctl execution if the driver is already bound to it.

[Saravanan KR (skramaja)]

https://review.opendev.org/#/c/673459/

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/os-net-config 10.4.1 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/os-net-config 9.4.1 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/os-net-config 8.5.1 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/os-net-config 11.2.0 release.