Comment 28 for bug 1786250

TL;DR - not the same bug, please open a new one

Hi,
well I only explained how to avoid the issue of the self FD access.
This is what this bug is about.

And your report doesn't have that anymore.
Please open a new bug for your issue.

For the things I see in what you posted seems to be about resolve.conf updates driven by/through strongswan. That really is a different issue.
The line:
#include <abstractions/nameservice>
Should cover resolve.conf actions, but we'd have to understand exactly how your strongswan is configured triggering this issue and then consider what/where to add apparmor rules for.

Please just use your last post for a new bug and feel free to copy&paste my reply as an answer.

From there add your config details especially related to resolve.conf updating and we can start thinking about it.