Juju plugins no longer work if there are no controllers

[Stuart Bishop]

Juju fails when there are no controllers, returning an error, before a plugin is invoked. This means that a plugin that creates a controller no longer works

$ cat ~/bin/juju-lxdstart
#!/bin/sh -e

if [ "$1" = "--description" ]; then
    echo "LXD Bootstrap"
    exit 0
fi

if [ "$1" = "--help" ]; then
    echo "usage: juju lxdstart"
    exit 0
fi

juju bootstrap --no-gui localhost lxd --config automatically-retry-hooks=false --config apt-http-proxy=http://10.0.4.1:3142/

$ juju lxdstart
ERROR No controllers registered.

Please either create a new controller using "juju bootstrap" or connect to
another controller that you have been given access to using "juju register".

Running the 'juju bootstrap' command manually works fine.

TBH I expect this is WONTFIX

[Anastasia (anastasia-macmood)]

We have recently changed cmd.Init() to cater for CAAS model command. I'll investigate to see what's going on...

Thank you for heads up \o/

[Anastasia (anastasia-macmood)]

PR against develop (heading into 2.5): https://github.com/juju/juju/pull/9101

[Anastasia (anastasia-macmood)]

I'll propose back-port as soon as 2.4 freeze is over.

[Anastasia (anastasia-macmood)]

@Stuart Bishop,

If you have means of verifying that the fix works for you, it'd be great \o/

[Anastasia (anastasia-macmood)]

PR for 2.4.3: https://github.com/juju/juju/pull/9117