[Bug 1549369] Re: Updating the apparmor manifest and deploying the new code without increasing app version does not trigger apparmor profile update on the device.

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: click (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to click in Ubuntu.
https://bugs.launchpad.net/bugs/1549369

Title:
  Updating the apparmor manifest and deploying the new code without
  increasing app version does not trigger apparmor profile update on the
  device.

Status in Client Developer Experience:
  Confirmed
Status in Canonical System Image:
  Confirmed
Status in click package in Ubuntu:
  Confirmed
Status in click-apparmor package in Ubuntu:
  Won't Fix

Bug description:
  On Krillin, as of rc-proposed r264,

  modifying the application apparmor manifest and then deploying the
  application to the device *without* increasing the app version will
  not trigger the apparmor profile update.

  As a consequence, the developer is left confused because the app is
  still complaining about apparmor denials even after he modified the
  apparmo manifest and deployed the new .click package.

  Deploying changes to an application without updating its version
  number is a quite common practice, especially while in development
  phase.

  That is why I believe we should fix this bug as soon as possible, to
  make life of developers easier.

  Reference of a similar bug, which was however more Snappy specific:
  https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1422744

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1549369/+subscriptions