diff options
| author | Martin Pitt <martin@piware.de> | 2018-07-08 19:49:21 +0200 |
|---|---|---|
| committer | Martin Pitt <martin@piware.de> | 2018-07-09 16:42:32 +0200 |
| commit | 207f5f4d9322ebd545491e5267e636a3ca07721f (patch) | |
| tree | bc8dc97edc7872fc9b87596dc21d26c38c5ad201 /test/networkd-test.py | |
| parent | 25ea58d37385af27301b7ad25e985eb15f421614 (diff) | |
| download | systemd-207f5f4d9322ebd545491e5267e636a3ca07721f.tar.gz | |
test: Reset systemd-resolved.service in networkd test
Like s-networkd.service itself, it can happen that s-resolved.service
runs into restart limits. Don't enforce a successful call, as on
machines without resolved the unit might not be loaded.
Diffstat (limited to 'test/networkd-test.py')
| -rwxr-xr-x | test/networkd-test.py | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/test/networkd-test.py b/test/networkd-test.py index de16ac1ad1..5ec670a733 100755 --- a/test/networkd-test.py +++ b/test/networkd-test.py @@ -177,7 +177,7 @@ Name=mybridge DNS=192.168.250.1 Address=192.168.250.33/24 Gateway=192.168.250.1''') - subprocess.check_call(['systemctl', 'reset-failed', 'systemd-networkd']) + subprocess.call(['systemctl', 'reset-failed', 'systemd-networkd', 'systemd-resolved']) subprocess.check_call(['systemctl', 'start', 'systemd-networkd']) def tearDown(self): @@ -263,7 +263,7 @@ class ClientTestBase(NetworkdTestingUtilities): self.assertTrue(out.startswith('-- cursor:')) self.journal_cursor = out.split()[-1] - subprocess.check_call(['systemctl', 'reset-failed', 'systemd-networkd']) + subprocess.call(['systemctl', 'reset-failed', 'systemd-networkd', 'systemd-resolved']) def tearDown(self): self.shutdown_iface() |