I'm still seeing the same problem after disabling AppArmor, so I think
it must be some other root problem.
On Wed, Oct 24, 2018 at 2:41 PM Neil Jerram wrote:
>
> Thanks so much for these hints, Erlon. I will look closer at AppArmor.
>
> Neil
>
> On Wed, Oct 24, 2018 at 1:41 PM Erlon Cruz wr
Thanks so much for these hints, Erlon. I will look closer at AppArmor.
Neil
On Wed, Oct 24, 2018 at 1:41 PM Erlon Cruz wrote:
>
> PS. Don't forget that if you change or disable AppArmor you will have to
> reboot the host so the kernel gets reloaded.
>
> Em qua, 24 de out de 2018 às 09:40,
PS. Don't forget that if you change or disable AppArmor you will have to
reboot the host so the kernel gets reloaded.
Em qua, 24 de out de 2018 às 09:40, Erlon Cruz
escreveu:
> I think that there's a change that AppArmor is blocking the access. Have
> you checked the dmesg messages related with
I think that there's a change that AppArmor is blocking the access. Have
you checked the dmesg messages related with apparmor?
Em sex, 19 de out de 2018 às 09:38, Neil Jerram escreveu:
> Wracking my brains over this one, would appreciate any pointers...
>
> Setup: Small test deployment with just
Wracking my brains over this one, would appreciate any pointers...
Setup: Small test deployment with just 3 compute nodes, Queens on Ubuntu
Bionic. The first compute node is an NFS server for
/var/lib/nova/instances, and the other compute nodes mount that as NFS
clients.
Problem: Sometimes, when
