Canonical Juju

diff-bundle incorrectly shows empty config

Bug #1866818 reported by Tom Haddon
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Low
Unassigned

Bug Description

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.

Revision history for this message
Richard Harding (rharding) wrote :

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.

Changed in juju:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Tom Haddon (mthaddon) wrote :

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

Richard Harding (rharding)
tags: added: bitesize
Revision history for this message
Paul Goins (vultaire) wrote :

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.

Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

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.

Changed in juju:
importance: Medium → Low
tags: added: expirebugs-bot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.