Based on the investigation, I think it is a bug in oslo, I have reported it in [1]. More details can be found at the bug description in [1]. Although [2] can eliminate the intermittent failure of test case, it should not be merged, because neutron-l3-agent actually uses ServiceLauncher. However, [2] is just to verify that ProcessLauncher will not have problem in the same circumstance. Merging [2] is non-sense.
Moreover, I doubt the meaning of the test in neutron a little, "neutron.service.Service.start" is mocked, the test case here is more like a test case for ServiceLauncher in oslo_service, to test if it can accept SIGHUP and restart services.
Anyway, anyone else is interested in this bug, feel free to participate in.
Based on the investigation, I think it is a bug in oslo, I have reported it in [1]. More details can be found at the bug description in [1]. Although [2] can eliminate the intermittent failure of test case, it should not be merged, because neutron-l3-agent actually uses ServiceLauncher. However, [2] is just to verify that ProcessLauncher will not have problem in the same circumstance. Merging [2] is non-sense.
Moreover, I doubt the meaning of the test in neutron a little, "neutron. service. Service. start" is mocked, the test case here is more like a test case for ServiceLauncher in oslo_service, to test if it can accept SIGHUP and restart services.
Anyway, anyone else is interested in this bug, feel free to participate in.
[1] https:/ /bugs.launchpad .net/oslo. service/ +bug/1523333 /review. openstack. org/#/c/ 251318/ 4/
[2] https:/