Streisand: "tor-bridge Reload the system_tor AppArmor profile for the override to take effect" is error

[HougeLangley]

Expected behavior:

Actual Behavior:

Steps to Reproduce:

1. Additional Details:

*Log output from Ansible or other relevant services (link to Gist for longer output):

TASK [tor-bridge : Reload the system_tor AppArmor profile for the override to take effect] *
fatal: [localhost]: FAILED! => {"changed": true, "cmd": ["apparmor_parser", "-r", "/etc/apparmor.d/system_tor"], "delta": "0:00:00.005799", "end": "2017-08-08 17:04:49.158690", "failed": true, "rc": 1, "start": "2017-08-08 17:04:49.152891", "stderr": "Cache read/write disabled: interface file missing. (Kernel needs AppArmor 2.4 compatibility patch.)\nWarning: unable to find a suitable fs in /proc/mounts, is it mounted?\nUse --subdomainfs to override.", "stderr_lines": ["Cache read/write disabled: interface file missing. (Kernel needs AppArmor 2.4 compatibility patch.)", "Warning: unable to find a suitable fs in /proc/mounts, is it mounted?", "Use --subdomainfs to override."], "stdout": "", "stdout_lines": []}

*Target Cloud Provider: Linode

Operating System of target host:

Operating System of client:

*Version of Ansible, using ansible --version : 2.3.20

*Output from git rev-parse HEAD in your Streisand directory : 49beda9c1a9c1880683fbb9f79b8b3ebc6529db0

[HougeLangley]

I have noticed that the kernel version used in Ubuntu 16.04 in Linode is 4.9. But in DigitalOcean is 4.4.

Some wrong with this ?

[HougeLangley]

Using default version of kernel could solved the problem.

https://www.linode.com/docs/tools-reference/custom-kernels-distros/run-a-distribution-supplied-kernel-with-kvm

[HougeLangley]

Problem solved. DO NOT USED KERNEL VERSION THE LINODE PROVIDED !!!

[cpu]

Problem solved. DO NOT USED KERNEL VERSION THE LINODE PROVIDED !!!

Did you create the Linode instance manually & then use Streisand to configure it in "existing server" or "localhost" mode? If so you've arrived at the right conclusion :-)

Streisand already uses a monkey-patch to the Linode python module to override the kernel to use a mainline kernel that works nicely with Wireguard. If you created the Linode instance through the ./streisand script by giving it your Linode API key this problem shouldn't have happened and might indicate a bug.

[HougeLangley]

@cpu Yes, I used localhost mode.

[cpu]

@HougeLangley Great! thanks for clarifying. Happy to hear there isn't a bug to squash! :mag_right: :beetle:

[littlebtc]

Bad news, I use ./streisand, using Tokyo-2 and my own API key, then the error still pop up:

TASK [tor-bridge : Reload the system_tor AppArmor profile for the override to take effect] ************************************************************************************************************************ fatal: [139.162.90.78]: FAILED! => {"changed": true, "cmd": ["apparmor_parser", "-r", "/etc/apparmor.d/system_tor"], "delta": "0:00:00.005714", "end": "2017-08-09 22:37:02.223269", "failed": true, "rc": 1, "start": "2017-08-09 22:37:02.217555", "stderr": "Cache read/write disabled: interface file missing. (Kernel needs AppArmor 2.4 compatibility patch.)\nWarning: unable to find a suitable fs in /proc/mounts, is it mounted?\nUse --subdomainfs to override.", "stderr_lines": ["Cache read/write disabled: interface file missing. (Kernel needs AppArmor 2.4 compatibility patch.)", "Warning: unable to find a suitable fs in /proc/mounts, is it mounted?", "Use --subdomainfs to override."], "stdout": "", "stdout_lines": []}

As told by Linode Manager, the kernel selected by streisand is Latest 64 bit (4.9.36-x86_64-linode85), which seems to build on July 17.

Time to open this issue again and fix that? :cry:

[cpu]

@littlebtc I just tried a fresh Linode provision using master and Tokyo-2. I can't reproduce the error. Are you still able to?

[cpu]

Closing this issue for now since I can't reproduce. Thanks!