apparmor denial during test runs for /home/phablet/autopilot/fakeenv/*/.cache/QML/

[Nicholas Skaggs]

Due to changes to support precompilation for qml applications, apparmor requires additional policy and directory setup to support the fakeenv environment. Affected application's autopilot tests will see errors similar to

apparmor="DENIED" operation="mkdir"
profile="com.ubuntu.calculator_calculator_1.3.329" name="/home/phablet/autopilot/fakeenv/tmpubm41n4c/.cache/QML/" pid=10637 comm="qmlscene"
requested_mask="c" denied_mask="c" fsuid=32011 ouid=32011

in there log.

[Ubuntu Phone Apps Jenkins Bot (ubuntu-phone-apps-jenkins-bot)]

Fix committed into lp:ubuntu-calculator-app at revision 333, scheduled for release in ubuntu-calculator-app, milestone 1.6

[Nicholas Skaggs (nskaggs)]

The suggested fix by Jamie didn't work in preliminary testing. That said due to the difficulties of releasing autopilot and maintaining these rules (see https://bugs.launchpad.net/ubuntu-app-launch/+bug/1376423), I feel it would be better to workaround them by dropping mocking support on the device and requiring the test runner to setup a clean environment. This assumption should work fine in CI as images are flash at the beginning of each test run.

By dropping mocking support, we don't use the fakeenv and thus these rules are not invoked (and therefore won't cause apparmor denials). See the MP for calculator as an example.

[Nicholas Skaggs (nskaggs)]

The click.rules file which used to exist in autopilot have moved. Once https://bugs.launchpad.net/ubuntu-app-launch/+bug/1376423 lands these rules should be cleaned up and removed. Until the proposed solution is implemented and then adopted by the tests in question, these apparmor denials will exist if the testcase utilizes the provided apparmor fakeenv setup.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.