ubuntu_qrt_apparmor test will fail on Azure 4.13 Standard-A0

[Po-Hsu Lin]

The test_regression_testsuite in ubuntu_qrt_apparmor test constantly fails on Azure 4.13 Standard-A0 node (passed on the other nodes).

Run parser regression tests ... (Applying patch r3446-fix-sysctl-syscall-detection.patch) (Applying patch tests-readdir-lp1674245.patch) (Applying patch tests-max_path-lp1692543.patch) (Applying patch r3701-tests-pivot_root.patch) (Applying patch r3702-tests-query_label.patch) ok
test_regression_testsuite (__main__.ApparmorTestsuites)
  preparing apparmor_2.10.95-0ubuntu2.9.dsc... done
 ERROR ubuntu_qrt_apparmor.test-apparmor.py ubuntu_qrt_apparmor.test-apparmor.py timestamp=1524115809 localtime=Apr 19 05:30:09 Test subprocess failed rc=9
 END ERROR ubuntu_qrt_apparmor.test-apparmor.py ubuntu_qrt_apparmor.test-apparmor.py timestamp=1524115826 localtime=Apr 19 05:30:26
Persistent state client._record_indent now set to 1
Persistent state client.unexpected_reboot deleted
END GOOD ---- ---- timestamp=1524115851 localtime=Apr 19 05:30:51

Not sure if it's because of insufficient memory:
$ free -m
              total used free shared buff/cache available
Mem: 647 251 59 2 336 225
Swap: 0 0 0

If you execute the "ubuntu-bug linux" command after this test, it will trigger an OOM event on it.
Please find the dmesg output here: http://paste.ubuntu.com/p/dH7mf5Vnzs/

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.13.0-1012-azure 4.13.0-1012.15
ProcVersionSignature: User Name 4.13.0-1012.15-username 4.13.13
Uname: Linux 4.13.0-1012-azure x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Thu Apr 19 06:27:08 2018
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-azure
UpgradeStatus: No upgrade log present (probably fresh install)

[Steve Beattie (sbeattie)]

Yes, this does look like an OOM condition. Does this happen now that linux-azure has moved to to the 4.15 kernel?

[Po-Hsu Lin (cypressyew)]

It seems that the test can pass with Azure 4.15 on StandardA0 without any problem.
Hence I will close this bug.
Thanks