Note that the fix is for the test, not for the kernel. The cause is that we don't have LSM stacking patches yet for 4.15, which makes changes to the config options.
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1751207 Title: test_072_config_security_apparmor in ubuntu_qrt_kernel_security failed on AMD64 Bionic Status in QA Regression Testing: New Status in linux package in Ubuntu: Incomplete Bug description: This issue could be found on AMD64, ppc64le, ARM64, s390x (not sure about i386, which was not tested because of the deployment issue in the last cycle) Result: FAIL: test_072_config_security_apparmor (__main__.KernelSecurityTest) CONFIG_SECURITY_APPARMOR enabled ---------------------------------------------------------------------- Traceback (most recent call last): File "./test-kernel-security.py", line 676, in test_072_config_security_apparmor self.assertEqual(self._get_config(default_apparmor_option), 'y') AssertionError: None != 'y' For the config in Bionic: $ grep -i apparmor /boot/config-4.15.0-10-generic CONFIG_SECURITY_APPARMOR=y CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1 CONFIG_SECURITY_APPARMOR_HASH=y CONFIG_SECURITY_APPARMOR_HASH_DEFAULT=y # CONFIG_SECURITY_APPARMOR_DEBUG is not set CONFIG_DEFAULT_SECURITY_APPARMOR=y CONFIG_DEFAULT_SECURITY="apparmor" And for the code itself: # Hardy and newer (Gutsy was a direct patch) def test_072_config_security_apparmor(self): '''CONFIG_SECURITY_APPARMOR enabled''' default_apparmor_option = 'DEFAULT_SECURITY_APPARMOR' if self.kernel_at_least('4.13'): default_apparmor_option = 'SECURITY_APPARMOR_STACKED' self.assertEqual(self._get_config('SECURITY_APPARMOR'), 'y') self.assertEqual(self._get_config(default_apparmor_option), 'y') self.assertEqual(self._get_config('SECURITY_APPARMOR_BOOTPARAM_VALUE'), '1') It's using CONFIG_DEFAULT_SECURITY_APPARMOR=y again in 4.15 kernel. Not sure if this is expected but I think this is the cause. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: User Name 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 AlsaDevices: total 0 crw-rw---- 1 root audio 116, 1 Feb 23 04:53 seq crw-rw---- 1 root audio 116, 33 Feb 23 04:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Feb 23 07:11:44 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R320 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=0845f9a0-ab8c-4dfa-8385-af21f2f2b9ad ro RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.171 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 0DY523 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd05/11/2012:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0DY523:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R320 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1751207/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
