snap enable removes complain for daemons

[sfg500]

Have a snap configured as forking daemon running installed in devmode.

before disable file /var/lib/snapd/apparmor/profiles/snap.test-daemon.run shows:
...
profile "snap.test-daemon.run" (attach_disconnected,complain)
...

After disable the snap everything is still ok.

after disable file /var/lib/snapd/apparmor/profiles/snap.test-daemon.run shows:
...
profile "snap.test-daemon.run" (attach_disconnected,complain)
...

But after executing snap enable the complain flag in apparmor profile is missing.

after enable file /var/lib/snapd/apparmor/profiles/snap.test-daemon.run shows:
...
profile "snap.test-daemon.run" (attach_disconnected)
...

snap list shows the snap still in devmode.

This behavior is additionally observed for snap configured as notify daemon.

Observed with Stable core version 16-2 1689 and release core version 16-2.26.4 2085

Is there a way to prevent the removal of the complain flag

[sfg500 (gwdev)]

The bug report is open for more than two months and so far no feedback has been given. Is there any chance that someone will have a look at it? Is there maybe an other place community where we could post this bug report and have a better chance to get feedback?

[Michael Vogt (mvo)]

Hi, sorry for the slow reply. We fixed a bug related to the "devmode" flag getting lost between enable,disable. Could you please check if snapd 2.29.X still has this problem? I am pretty confident it is fixed now.

[Launchpad Janitor (janitor)]

[Expired for Snappy because there has been no activity for 60 days.]