WireGuard failure on Tumbleweed

Hi all,
This issue may be closely related to Zypper dup 23 hours ago - Wireguard fails, Samba fails. However, as my WG problem is not related to Samba, I thought opening a new thread would be OK.
There was an issue in Tumbleweed where previously functional WireGuard tunnels all of a sudden were failing; the aforementioned thread provides details. Bugzilla (https://bugzilla.opensuse.org/show_bug.cgi?id=1265394) says the issue is fixed.

Unfortunately, it is not fixed for me. The behaviour has definitely changed, but I still cannot start the WG VPN tunnel. When I try to start it with wg-quick, the following text appears in the console window:
`
[#] ip link add dev WG611 type wireguard

[#] wg addconf WG611 /dev/fd/63

[#] ip -4 address add 192.168.10.209/24 dev WG611

[#] ip -6 address add fd07:d4b:e145::209/64 dev WG611

[#] ip link set mtu 1420 up dev WG611

[#] mount `192.168.10.1 fd07:d4b:e145::b6fc:7dff:fefb:e98f’ /etc/resolv.conf

unshare: cannot change root filesystem propagation: Permission denied `

The same script with the same WG configuration file works perfectly OK on Leap 15.6.

Has anyone an idea how to get this working again?

@afalb Likely SELinux, or are you running Apparmor? If SELinux see the Forum side panel for a link to the SELinux Portal and some step to test, likely a bug report will be needed.

I had AppArmor activated. After disabling it and rebooting the machine the VPN tunnel is working again.

@afalb Then re-open the bug and add your error information to it…

@cboltz or do you have an idea?

Bugzilla item re-opened.

Reconfigured my system to use SELinux instead of AppArmor (according to https://en.opensuse.org/Portal:SELinux/Setup). Result: WireGuard working as expected.