Juju appears to succeed but actually doesn't upload the charms repository
John Arbash Meinel
john at arbash-meinel.com
Fri Sep 6 11:50:22 UTC 2013
-----BEGIN PGP SIGNED MESSAGE-----
On 2013-09-06 14:40, Peter Waller wrote:
> Hi All,
> We just encountered a really nasty problem: a "juju upgrade-charm"
> was appearing to cause the config-changed hook to run, and we were
> seeing what looked like a correct deploy, but in fact the changes
> in the local charms repository were not being reflected on the
> remote server.
We do have a task about "juju client should show WARNINGs by default",
though apparently it wasn't actually turned into a bug.
So feel free to submit one about this.
As for whether the build step should be an ERROR (fatal) vs a WARNING,
it does sound like we couldn't actually do what you asked, and it
should be an ERROR. I don't quite understand why changing the
executable bit would be a warning (vs debug/info) but maybe it should
be shown to the user by default.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----
More information about the Juju