Closed ypid closed 7 years ago
I have not experianced such problems before. keyhole.pubsrv.ypid.de (Debian jessie) has AppArmor enabled and hosts LXC containers. Maybe for Ubuntu there is configuration needed? You could try to disable AppArmor:
service apparmor teardown
service apparmor stop
aa-status
# Should show 0 loaded profiles.
But I am not sure if that would fix the problem.
Also, maybe try to run the debops-contrib.apparmor before or something like touch /etc/apparmor.d/tunables/global
.
@ypid The AppArmor role was running in the Travis-CI test, I disabled it with no effect. Let me try tearing down AppArmor first to see what happens.
Trying to fix AppArmor didn't work, but! It seems that .travis.yml
does not have sudo: True
, so it uses the Docker container infrastructure for the builds. @ypid, can you add sudo: True
to the Travis config, maybe that will work?
Sure. Thanks for looking into this!
@ypid Looks like disabling AppArmor on Trusty lets the rest of the role pass, it seems that the debops-contrib.apparmor
does not ensure that a required directory exists. Do you want to fix that (test it on Trusty) before merging debops.lxc
changes?
@drybjed Sure, I can do that later today. Tests for debops-contrib.apparmor
pass on precise (https://travis-ci.org/debops-contrib/ansible-apparmor)
But the debops.lxc
role also failed before on precise. I switched the test to Trusty to see if that changes something.
Good catch, thanks. All fixed.
I've looked into this PR some more, looks like AppArmor on Travis-CI is preventing the correct installation, the error seems to be:
I tried to disable the AppArmor role in the playbook, but I guess it's already installed. Maybe there's a way to disable AppArmor in the Travis-CI build?