Re: Is there a way to let juju know that an lxc container has gone away and isn't coming back?

On 08/04/16 15:03, Pete Vander Giessen wrote: > @Charles: Aha! The various destroy commands don't have a --force flag; I > didn't know about the "remove-machine" command, which does accept --force. > > That seemed to work. Thank you :-) > We should definitely clean that up in 2.0 final. Mark --

Re: Is there a way to let juju know that an lxc container has gone away and isn't coming back?

Happy to help! Glad it got you sorted. All the best > On Apr 8, 2016, at 10:03 AM, Pete Vander Giessen wrote: > > @Charles: Aha! The various destroy commands don't have a --force flag; I > didn't know about the "remove-machine" command, which does accept --force. > > That

Re: Is there a way to let juju know that an lxc container has gone away and isn't coming back?

@Charles: Aha! The various destroy commands don't have a --force flag; I didn't know about the "remove-machine" command, which does accept --force. That seemed to work. Thank you :-) ~ PeteVG On Fri, Apr 8, 2016 at 9:47 AM Charles Butler wrote: > I haven't

Re: Is there a way to let juju know that an lxc container has gone away and isn't coming back?

I haven't validated this but you can try to remove the machine forcibly Juju remove-machine ## --force That should force removal of the container from the controller and let you destroy-service to remove it from the model. > On Apr 8, 2016, at 8:56 AM, Pete Vander Giessen

Is there a way to let juju know that an lxc container has gone away and isn't coming back?

Hi All, Let's say that someone (okay, me) is experimenting with juju2 (develop) locally, and I've rudely destroyed an lxc container that had a juju charm deployed to it (lxc stop && lxc delete ). Is there a way to convince juju that the charm is no longer deployed? juju destroy-service and juju