diff-bundle incorrectly shows empty config

[Tom Haddon]

I'm using 2.8-beta1-focal-amd64. I deployed the "media-simple" bundle, and then ran juju diff-bundle bundle.yaml. Some trimmed output here:

applications:
  mysql:
    series:
      bundle: ""
      model: trusty
    options:
      block-size:
        bundle: 5
        model: null

Running juju config mysql block-size I get "5" as the output so I'm not sure why it's saying "null" in the model.

[Richard Harding (rharding)]

Do you know if the 5 value is the default? I wonder if it hasn't been "set" by an operator in the model and that's why we have the null. We'll look into it.

[Tom Haddon (mthaddon)]

The default is 5 in the version of the charm I was testing with, fwiw.

[Paul Goins (vultaire)]

I can confirm this. I'm using "juju diff-bundle" on a customer cloud now, comparing the source bundle from field against what's running live, and I get significant noise. Every single unspecified config value with a non-null default value seems to show up as a delta between the bundle and model.

[Canonical Juju QA Bot (juju-qa-bot)]

This Medium-priority bug has not been updated in 60 days, so we're marking it Low importance. If you believe this is incorrect, please update the importance.