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

2016-04-08 Thread Mark Shuttleworth 
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

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

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

2016-04-08 Thread Charles Butler 
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 seemed to work. Thank you :-)
> 
> ~ PeteVG
> 
>> On Fri, Apr 8, 2016 at 9:47 AM Charles Butler  
>> wrote:
>> 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  wrote:
>> >
>> > 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 destroy-unit both fail, because juju cannot 
>> > connect to the machine. Is there a way, short of clobbering 
>> > ~/.local/shrare/juju and attempting to start from scratch, of making juju 
>> > let go of the charm?
>> >
>> > Thank you in advance,
>> >
>> > ~ PeteVG
>> > --
>> > Juju mailing list
>> > Juju@lists.ubuntu.com
>> > Modify settings or unsubscribe at: 
>> > https://lists.ubuntu.com/mailman/listinfo/juju
> -- 
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/juju
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

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

2016-04-08 Thread Pete Vander Giessen 
@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 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 
> wrote:
> >
> > 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 destroy-unit both fail, because juju cannot
> connect to the machine. Is there a way, short of clobbering
> ~/.local/shrare/juju and attempting to start from scratch, of making juju
> let go of the charm?
> >
> > Thank you in advance,
> >
> > ~ PeteVG
> > --
> > Juju mailing list
> > Juju@lists.ubuntu.com
> > Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

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

2016-04-08 Thread Charles Butler 
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  wrote:
> 
> 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 destroy-unit both fail, because juju cannot connect 
> to the machine. Is there a way, short of clobbering ~/.local/shrare/juju and 
> attempting to start from scratch, of making juju let go of the charm?
> 
> Thank you in advance,
> 
> ~ PeteVG
> -- 
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/juju

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

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

2016-04-08 Thread Pete Vander Giessen 
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 destroy-unit both fail, because juju cannot
connect to the machine. Is there a way, short of clobbering
~/.local/shrare/juju and attempting to start from scratch, of making juju
let go of the charm?

Thank you in advance,

~ PeteVG
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju