openvswitch service is restarted when running os-net-config with --no-activate

[zenghui.shi]

if we run os-net-config with option --no-activate[1], it's expecting that there is no network interruption during the cmd execution, for example, any of network interfaces or openvswitch service should not be restarted, but in a dpdk environment, when dpdk port config file(ifcfg-dpdkx) is changed, it will cause restart of openvswitch service.

[1]: os-net-config --no-activate -c /etc/os-net-config/config.json -v --detailed-exit-codes

[Saravanan KR (skramaja)]

https://review.openstack.org/#/c/548006/

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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