I can confirm that booting with "apparmor=0" added to kernel command line works around the issue.
This host runs lxd containers, so from the security standpoint running it without apparmor is not acceptable. However this proves there is an apparmor bug.
I can confirm that booting with "apparmor=0" added to kernel command line works around the issue.
This host runs lxd containers, so from the security standpoint running it without apparmor is not acceptable. However this proves there is an apparmor bug.