Comment # 5 on bug 1144527 from Dan ��erm��k

(In reply to James Fehlig from comment #4)
> (In reply to James Fehlig from comment #3)
> > Can you re-enable apparmor and capture output of /var/log/audit/audit.log
> > when reproducing the bug? It should contain a DENIAL message from apparmor
> > with more details.
> 
> Hi Dan, any chance you can provide this info? Or if disabling apparmor is
> sufficient for your needs we can close this bug. Thanks!

Sorry for the late reply James. I have re-enabled Apparmor (systemctl start
unmask apparmor, followed by a reboot) on the machine in question and retried
the whole vagrant pipeline. (Un)Fortunately, there was no failure whatsoever.

I'll keep apparmor enabled for a while and watch out in case this issue
resurfaces.