it looks like more than one issue, from there. Comment #12 aligns with this report. But there are other 3.1.5 failures around mount, where there is no mount rule in the profile. So the access denials would be expected.
Could some of this be an issue with how snapd is detecting if apparmor supports a given mount rule.
the suse version of this bug has more activity https:/ /bugzilla. opensuse. org/show_ bug.cgi? id=1211989
it looks like more than one issue, from there. Comment #12 aligns with this report. But there are other 3.1.5 failures around mount, where there is no mount rule in the profile. So the access denials would be expected.
Could some of this be an issue with how snapd is detecting if apparmor supports a given mount rule.