Comment 5 for bug 1929908

I have found that if the bundle contains values for a charm option where the value in the bundle is the same as the charm default, then the diff which is done includes such config values in the change set, because only non-default values are included when doing the diff of what's in the juju model vs what's in the new bundle yaml.

So the ceph-osd charm has this

aa-profile-mode | string
Default: disable

If the bundle has this:
  ceph-osd:
     charm: ceph-osd
      options:
        aa-profile-mode: disable

Then the export and redeploy workflow will think the aa-profile-name has changed since it is filtered out of what's been deployed before the client side diff is done.

I also noticed testing on 2.9 that juju thinks the charm itself needs to be re-uploaded.