| 2021-01-29 13:43:09 |
Corey Bryant |
description |
I noticed this issue with the ovn-chassis charm's pause/resume tests failing. Pause will stop the ovn-host service and the test will check if any ovn-controller pids exist after the stop, and in fact they did still exist.
Stopping and starting ovn-host service is typically fine and the ovn-controller pids get cleaned up when stopped. For example:
https://paste.ubuntu.com/p/gq9VXWN25y/
The same details are in the attached stop-start-good.txt file.
However, if openvswitch-switch is restarted prior to the stop/start of ovn-host, it seems to cause issues where ovn-controller pids don't get cleaned up. For example:
https://paste.ubuntu.com/p/Tn6wzY7gWH/
The same details are in the attached stop-start-bad.txt file.
I haven't looked into it much but wondering if it may be an issue in the upstream utilities/ovn-ctl script. |
I noticed this issue with the ovn-chassis charm's pause/resume tests failing. Pause will stop the ovn-host service and the test will check if any ovn-controller pids exist after the stop, and in fact they did still exist.
Stopping and starting ovn-host service is fine if openvswitch-switch hasn't been restarted. The ovn-controller pids get cleaned up when ovn-host is stopped. For example:
https://paste.ubuntu.com/p/gq9VXWN25y/
The same details are in the attached stop-start-good.txt file.
However, if openvswitch-switch is restarted prior to the stop/start of ovn-host, it seems to cause issues where ovn-controller pids don't get cleaned up. For example:
https://paste.ubuntu.com/p/Tn6wzY7gWH/
The same details are in the attached stop-start-bad.txt file.
I haven't looked into it much but wondering if it may be an issue in the upstream utilities/ovn-ctl script. |
|
