openvswitch service is restarted when running os-net-config with --no-activate
Bug #1751955 reported by
zenghui.shi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
zenghui.shi |
Bug Description
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-
summary: |
- openvswitch service is restarted with --no-activate + openvswitch service is restarted when running os-net-config with --no- + activate |
Changed in tripleo: | |
milestone: | queens-rc1 → rocky-1 |
Changed in tripleo: | |
milestone: | rocky-1 → rocky-2 |
Changed in tripleo: | |
milestone: | rocky-2 → rocky-3 |
Changed in tripleo: | |
milestone: | rocky-3 → rocky-rc1 |
Changed in tripleo: | |
milestone: | rocky-rc1 → stein-1 |
Changed in tripleo: | |
milestone: | stein-1 → stein-2 |
Changed in tripleo: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
https:/ /review. openstack. org/#/c/ 548006/