Re: killing old dead controllers
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 Bidwellwrote: > 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 MachinesHA Version > lxd-test-admin superuser lxd/localhost >2 1 none 2.0.2 > test-lxd* default admin superuser localhost/ > localhost 2 1 none 2.1.3 > > lxc list produces: > > root@juju:~# lxc list > +--+---+--+--+--+---+ > | NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS | > +--+---+--+--+--+---+ > > Any attemtp to remove, delete, kill, or destroy results in the command > hanging and never coming back. I have been trying to develop some > local charms using lxd. I know that this kind of testing and > developemnt is hard on vms/containers, but throwing away the vm and > reinstalling ubuntu is probably not the desired behaviour. > -- > Daniel Bidwell > > > -- > Juju-dev mailing list > juju-...@lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/ > mailman/listinfo/juju-dev > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: killing old dead controllers
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 Bidwellwrote: > 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 MachinesHA Version > lxd-test-admin superuser lxd/localhost >2 1 none 2.0.2 > test-lxd* default admin superuser localhost/ > localhost 2 1 none 2.1.3 > > lxc list produces: > > root@juju:~# lxc list > +--+---+--+--+--+---+ > | NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS | > +--+---+--+--+--+---+ > > Any attemtp to remove, delete, kill, or destroy results in the command > hanging and never coming back. I have been trying to develop some > local charms using lxd. I know that this kind of testing and > developemnt is hard on vms/containers, but throwing away the vm and > reinstalling ubuntu is probably not the desired behaviour. > -- > Daniel Bidwell > > > -- > Juju-dev mailing list > Juju-dev@lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/ > mailman/listinfo/juju-dev > -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
killing old dead controllers
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 Machines HA Version lxd-test-admin superuser lxd/localhost 2 1 none 2.0.2 test-lxd* default admin superuser localhost/localhost 2 1 none 2.1.3 lxc list produces: root@juju:~# lxc list +--+---+--+--+--+---+ | NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS | +--+---+--+--+--+---+ Any attemtp to remove, delete, kill, or destroy results in the command hanging and never coming back. I have been trying to develop some local charms using lxd. I know that this kind of testing and developemnt is hard on vms/containers, but throwing away the vm and reinstalling ubuntu is probably not the desired behaviour. -- Daniel Bidwell-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
killing old dead controllers
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 Machines HA Version lxd-test-admin superuser lxd/localhost 2 1 none 2.0.2 test-lxd* default admin superuser localhost/localhost 2 1 none 2.1.3 lxc list produces: root@juju:~# lxc list +--+---+--+--+--+---+ | NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS | +--+---+--+--+--+---+ Any attemtp to remove, delete, kill, or destroy results in the command hanging and never coming back. I have been trying to develop some local charms using lxd. I know that this kind of testing and developemnt is hard on vms/containers, but throwing away the vm and reinstalling ubuntu is probably not the desired behaviour. -- Daniel Bidwell-- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev