Policy doesn't update when installing Snappy app with same version

[Nikolay]

I tried to build snap package for Ubuntu Snappy build for Beagle Bone Black. I make this package for IoT device, it contains AllJoyn ( https://allseenalliance.org/developers/learn ), it require lots of dbus features. That's why I have to write my own apparmor profile.

After first attempt I've got this message:
[ 499.786552] audit: type=1400 audit(1421754939.200:22): apparmor="DENIED" operation="bind" profile="my-app_my-app-service_1.0.0" pid=1453 comm="alljoyn-daemon" family="unix" sock_type="stream" protocol=0 requested_mask="bind" denied_mask="bind" addr="@alljoyn"

Then I've added line to profile:
  unix (create,bind,listen,send,receive,setopt,connect) type=stream,

rebuild the snap, call 'snappy-remote install', but this message still appears. I even removed profile file in /var/lib/apparmor/profiles dir (that line was in file) and reboot board, but this message still appears.

Only after complete snap removal(snappy uninstall) and clean install this message disappear.

[Jamie Strandboge (jdstrand)]

Thank you for using Ubuntu and filing a bug. I'm guessing you didn't rev the version and instead installed the same version. There is a limitation in 'click' (the underlying packaging tool that is being replaced) that makes it not run its hooks when installing a package with the same version. If you are using the normal confinement ("apparmor" is used in the underlying click manifest), then you can workaround this by performing the following after installing a package with the same version:
$ sudo aa-clickhook -f

If you are supplying your own profile ("apparmor-profile" is used in the underlying click manifest), then you can workaround this by performing the following after installing a package with the same version:
$ sudo aa-profile-hook -f

Also, Is there any reason for this bug to be private?

[Jamie Strandboge (jdstrand)]

This is a known limitation in click. Since we will be moving away from click in favor of snappy and because known workarounds exists, marking this bug as Won't Fix.

[Nikolay (2xl)]

yeah, I didn't change snap revision.
Thank you for fast answer and clear explanation.
There is no reason to make it private. I've changed it to public. Most probably, I've incidentally click somewhere on page, sorry for that.

[Andrea Bernabei (faenil)]

Since the phones are still using click, we have to fix it on click side as well.

 I created https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1549369 to track that