Tests in networking_sfc.functional.test_server module are testing how
service is handling SIGHUP signal.
Recently this was changed in Oslo.service with [1] and our tests
were failing because they were still expecting that after sending
SIGHUP to the process, stop() and than start() method will be called.
But as our services uses "mutate" as restart method, since [1] such
process don't executes stop() and start() after SIGHUP. It now executes
only reset() method.
Similar change was recently done in Neutron's functional tests in [2].
This patch reflects that change in networking-sfc functional tests.
Reviewed: https:/ /review. opendev. org/684977 /git.openstack. org/cgit/ openstack/ networking- sfc/commit/ ?id=0644862c8be edd902a7d739be5 24699edc9b61d3
Committed: https:/
Submitter: Zuul
Branch: master
commit 0644862c8beedd9 02a7d739be52469 9edc9b61d3
Author: Slawek Kaplonski <email address hidden>
Date: Thu Sep 26 11:06:41 2019 +0200
[Functional tests] Fix SIGHUP handling tests
Tests in networking_ sfc.functional. test_server module are testing how
service is handling SIGHUP signal.
Recently this was changed in Oslo.service with [1] and our tests
were failing because they were still expecting that after sending
SIGHUP to the process, stop() and than start() method will be called.
But as our services uses "mutate" as restart method, since [1] such
process don't executes stop() and start() after SIGHUP. It now executes
only reset() method.
Similar change was recently done in Neutron's functional tests in [2].
This patch reflects that change in networking-sfc functional tests.
[1] https:/ /review. opendev. org/#/c/ 641907/ /review. opendev. org/#/c/ 680001/
[2] https:/
Change-Id: I22629c59da983f 47ef8b1862afb9a 62bdfd78b02
Closes-Bug: #1842659