If the machines are just gone (you manually destroyed them via 'lxc
stop/delete'). You can just do:
juju unregister lxd-test
It will remove it from the local registry without trying to tear anything
down.
John
=:->
On Tue, Jun 13, 2017 at 8:17 AM, Daniel Bidwell wrote:
I have a machine with 2 dead controllers that I can't figure out how to
delete. A "juju controllers" produces the following:
root@juju:~# juju controllers
Use --refresh flag with this command to see the latest information.
Controller ModelUser Access Cloud/Region Models
Yes, and this too has been corrected. You should expect releases to flow
down to level of risk. So, when 2.2 releases, beta, candidate and stable
will all point to the 2.2 revision (until the first beta for 2.3, and so
on).
channels:
latest/stable:2.1.3 (1922) 24MB
Nicholas,
Thanks. beta is still 2.2rc1. Should it be 2.2rc2 also?
Jason
On Mon, Jun 12, 2017 at 11:15 AM, Nicholas Skaggs <
nicholas.ska...@canonical.com> wrote:
> Thanks for the heads-up Jason. Yes, small snafu with publishing the
> builds. Edge builds are tracking develop (2.3-alpha1) and
I noticed that for the juju snap, edge and beta channels have older
releases than candidate. Shouldn't they always be at least the same
version as candidate, if not newer?
stable:2.1.3 (1922) 24MB classic
candidate: 2.2-rc2 (1929) 25MB classic
beta:
n techniques.
>
> - Menno
> -- next part --
> An HTML attachment was scrubbed...
> URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/
> 20170612/59c96e86/attachment-0001.html>
>
> --