From b0d36a876d8da6cccffa00156dea0782a7ad918c Mon Sep 17 00:00:00 2001 From: elajkat Date: Fri, 6 Sep 2019 15:52:30 +0200 Subject: [PATCH] Add note about apparmor issue with fullstack tests Change-Id: I9e3bf0562264d564c8faf56af9f451e2fbd4d6ce --- TESTING.rst | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/TESTING.rst b/TESTING.rst index 10db3c9ab8d..62bd47137c7 100644 --- a/TESTING.rst +++ b/TESTING.rst @@ -613,6 +613,21 @@ to look if your test is failing. The fullstack test suite assumes 240.0.0.0/4 (Class E) range in the root namespace of the test machine is available for its usage. +Fullstack tests execute a custom dhclient-script. From kernel version 4.14 onward, +apparmor on certain distros could deny the execution of this script. To be sure, +check journalctl :: + + sudo journalctl | grep DENIED | grep fullstack-dhclient-script + +To execute these tests, the easiest workaround is to disable apparmor :: + + sudo systemctl stop apparmor + sudo systemctl disable apparmor + +A more granular solution could be to disable apparmor only for dhclient :: + + sudo ln -s /etc/apparmor.d/sbin.dhclient /etc/apparmor.d/disable/ + API & Scenario Tests ~~~~~~~~~~~~~~~~~~~~