© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Hello Jamon,
It's nice to talk to you again. The issue here was that Juju would store the path to the credentials file and not the actual configuration therein. Other portions of Juju would then expect the configuration and would complain that they found "/" (the first character of an absolute path) rather than legitimate YAML. We fixed this by ensuring any credential configuration stored as a path will be "finalized" to its content before use. I will look into this to gather why you still see the problem.
I understand that you have a 2.0.3 controller and a 2.3.7 client and are seeing failures on `upgrade-juju --dry-run`. I will poke at this a bit and let you know if it is the same issue as above or not. Thank you for reporting the error.