Comment 3 for bug 1667199
Revision history for this message
| Michael Nelson (michael.nelson) wrote Re: Default '' config options not present during config-changed | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
OK, I needed to look into this again today (after my work-around had it's own issues), and was able to reproduce it both on the original cloud, as well as locally.
Details here [1] but it looks like the issue isn't the default values, but instead whether the deployment is configured to send empty values for some options - and if so - juju seems not to include those options at all in the unit's config-get, rather than including them with their set empty values.
[1] http://