autopkgtest: boot-and-services test fails in armhf containers

[Balint Reczey]

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/armhf/s/systemd/20190902_092319_bc0af@/log.gz

...
test_udev (__main__.ServicesTest) ... skipped 'udev does not work in containers'

======================================================================
ERROR: test_profile (__main__.AppArmorTest)
AppArmor confined unit
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/tmp/autopkgtest.3bj70k/build.TYC/src/debian/tests/boot-and-services", line 286, in test_profile
    subprocess.check_call(['apparmor_parser', '-r', '-v', aa_profile.name])
  File "/usr/lib/python3.7/subprocess.py", line 347, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['apparmor_parser', '-r', '-v', '/tmp/aa_violator.hg3olay4']' returned non-zero exit status 243.

----------------------------------------------------------------------
Ran 23 tests in 5.848s

FAILED (errors=1, skipped=5)

...

[Dan Streetman (ddstreet)]

I have this open against debian:
https://salsa.debian.org/systemd-team/systemd/merge_requests/51

[Balint Reczey (rbalint)]

@ddstreet Thanks, I already fixed it by masking Apparmor test only on arm*

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9d3b35df77aa939365563a4edaee54ebb7f559a3

[Dan Streetman (ddstreet)]

> masking Apparmor test only on arm

er, the is_container check is enough (although just ignores the problem), you don't need to also check for arm.

[Balint Reczey (rbalint)]

@ddstreet True, but it ran fine when running the test locally with standard lxd virt on amd64, so I did not want to skip it on all containers.
I'll be happy to merge it away when the Salsa PR lands in Debian and gets merged to Ubuntu.

[Balint Reczey (rbalint)]

This is fixed in Eoan's 242-6ubuntu1.