Hi All,
Thank you for all the advice. @Andrew Wilkins: turning up logging unstuck
me. :-)
Details follow, for those interested:
I've been mis-stating the root of the problem. It's not a blank value in
config.yaml, it's a blank value in the "options" for haproxy in the
bundle.yaml. The good news
Hi Pete,
I recently modified the GUI to use the new `configYAML` field. To do so I
took the JSON that we normally sent in the `config` argument and passed it
as the `configYAML` argument. You can see the PR[0] for the change made and
a little code comment as to why.
If you'd like an easy way to
Note my analysis could be incorrect. Anastasia has been digging into the
bug directly and is seeing 'nil' as a value get added to the content it the
database, and then get passed through to config-get. It appears that we
have a bug in that we have 2 code paths for taking charm defaults + charm
On Wed, Mar 1, 2017 at 6:42 AM Pete Vander Giessen <
pete.vandergies...@canonical.com> wrote:
> Hi All,
>
> I'm currently working on getting python-libjuju to successfully deploy the
> landscape-dense-maas bundle. It fails, as outlined in
> https://bugs.launchpad.net/juju/+bug/1651260.
>
>
Hi All,
I'm currently working on getting python-libjuju to successfully deploy the
landscape-dense-maas bundle. It fails, as outlined in
https://bugs.launchpad.net/juju/+bug/1651260.
(python-libjuju is a Python client that talks to Juju's websocket API; I'm
currently using it inside the matrix
