Re: JAAS confusion

[Pete Vander Giessen]

> So just changing your client isn't going to fix the issue, as it is a
server side issue that is refusing to destroy the models.

Aha. That makes more sense, actually.

I'll look forward to testing things out once things update on the JaaS side
:-)

~ PeteVG

On Thu, Oct 12, 2017 at 3:46 PM John Meinel  wrote:

> So just changing your client isn't going to fix the issue, as it is a
> server side issue that is refusing to destroy the models.
>
> https://bugs.launchpad.net/bugs/1714409
>
> Is at least one of them that might be relevant for your issue.
>
> I also know that we have:
>  https://bugs.launchpad.net/bugs/1721786
>
> which is a different iteration of remove-model failing (we changed a lot
> of code to use a shared pool of information about models, and it has a
> slightly different issue as models get removed). But that one is 2.3
> specific and I expect it to be fixed by early next week.
>
> John
> =:->
>
> On Thu, Oct 12, 2017 at 11:59 AM, Pete Vander Giessen <
> pete.vandergies...@canonical.com> wrote:
>
>> Hi All,
>>
>> > I think the inability to remove a model that is half-dead might be
>> fixed already in 2.3 but has to do with an issue around 2 critical
>> documents that define a model, and one of them has been removed but not the
>> other, which leads to a bunch of code that gets a different view of whether
>> the model exists or not.
>>
>> I have a few models stuck in a state where I can't remove them. I gave
>> juju 2.3 a try via the edge channel in the snap
>> (2.3-beta2+develop-79cd92d), and it looks like the error message is
>> different, but I still can't remove them.
>>
>> The old error message:
>>
>> ERROR cannot destroy model: failed to destroy model: state changing too
>> quickly; try again soon
>>
>> The new error message:
>>
>> ERROR cannot destroy model: context deadline exceeded
>>
>> Is there an open bug that I can paste error messages and logs to?
>>
>> ~ PeteVG
>>
>>
>>
>> On Mon, Oct 9, 2017 at 4:18 PM John Meinel 
>> wrote:
>>
>>> The 6 accessible models is gone in 2.3 (IIRC), because it was actually
>>> just reflecting some locally cached information about model numbers, but
>>> wasn't actually being kept up to date properly.
>>>
>>> I think the inability to remove a model that is half-dead might be fixed
>>> already in 2.3 but has to do with an issue around 2 critical documents that
>>> define a model, and one of them has been removed but not the other, which
>>> leads to a bunch of code that gets a different view of whether the model
>>> exists or not.
>>>
>>> A different explanation could be that you create a model with the same
>>> name with a different client and thus its actually the underlying UUID
>>> doesn't exist, but there is a model collision. (Your local client new a
>>> model named 'mymodel' with UUID 1234, but you had a different client that
>>> deleted that model and created a new 'mymodel' with UUID 3456, but when
>>> you're trying to 'juju destroy-model' we are using the 1234 UUID again. I'm
>>> brainstorming, though, and wouldn't say concretely that it is definitely
>>> true.)
>>>
>>> John
>>> =:->
>>>
>>>
>>> On Mon, Oct 9, 2017 at 9:42 PM, Tom Barber  wrote:
>>>
 Hello folks

 Couple of random questions:

 juju destroy-model mymodel
 WARNING! This command will destroy the "mymodel" model.
 This includes all machines, applications, data and other resources.

 Continue [y/N]? y
 ERROR cannot connect to API: model "mymodel" has been removed from the
 controller, run 'juju models' and switch to one of them.
 There are 6 accessible models on controller "jaas".

 juju models
 Controller: jaas

 Model  Cloud/Region   Status Machines  Cores  Access  Last
 connection
 mymodelaws/eu-west-1  available 5  9  -   never
 connected



 2 things in this output, firstly how do I delete the model that seems
 stuck?

 secondly what is the 6 accessible models bit talking about?

 Thanks

 Tom

 --
 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: JAAS confusion

[John Meinel]

So just changing your client isn't going to fix the issue, as it is a
server side issue that is refusing to destroy the models.

https://bugs.launchpad.net/bugs/1714409

Is at least one of them that might be relevant for your issue.

I also know that we have:
 https://bugs.launchpad.net/bugs/1721786

which is a different iteration of remove-model failing (we changed a lot of
code to use a shared pool of information about models, and it has a
slightly different issue as models get removed). But that one is 2.3
specific and I expect it to be fixed by early next week.

John
=:->

On Thu, Oct 12, 2017 at 11:59 AM, Pete Vander Giessen <
pete.vandergies...@canonical.com> wrote:

> Hi All,
>
> > I think the inability to remove a model that is half-dead might be
> fixed already in 2.3 but has to do with an issue around 2 critical
> documents that define a model, and one of them has been removed but not the
> other, which leads to a bunch of code that gets a different view of whether
> the model exists or not.
>
> I have a few models stuck in a state where I can't remove them. I gave
> juju 2.3 a try via the edge channel in the snap
> (2.3-beta2+develop-79cd92d), and it looks like the error message is
> different, but I still can't remove them.
>
> The old error message:
>
> ERROR cannot destroy model: failed to destroy model: state changing too
> quickly; try again soon
>
> The new error message:
>
> ERROR cannot destroy model: context deadline exceeded
>
> Is there an open bug that I can paste error messages and logs to?
>
> ~ PeteVG
>
>
>
> On Mon, Oct 9, 2017 at 4:18 PM John Meinel  wrote:
>
>> The 6 accessible models is gone in 2.3 (IIRC), because it was actually
>> just reflecting some locally cached information about model numbers, but
>> wasn't actually being kept up to date properly.
>>
>> I think the inability to remove a model that is half-dead might be fixed
>> already in 2.3 but has to do with an issue around 2 critical documents that
>> define a model, and one of them has been removed but not the other, which
>> leads to a bunch of code that gets a different view of whether the model
>> exists or not.
>>
>> A different explanation could be that you create a model with the same
>> name with a different client and thus its actually the underlying UUID
>> doesn't exist, but there is a model collision. (Your local client new a
>> model named 'mymodel' with UUID 1234, but you had a different client that
>> deleted that model and created a new 'mymodel' with UUID 3456, but when
>> you're trying to 'juju destroy-model' we are using the 1234 UUID again. I'm
>> brainstorming, though, and wouldn't say concretely that it is definitely
>> true.)
>>
>> John
>> =:->
>>
>>
>> On Mon, Oct 9, 2017 at 9:42 PM, Tom Barber  wrote:
>>
>>> Hello folks
>>>
>>> Couple of random questions:
>>>
>>> juju destroy-model mymodel
>>> WARNING! This command will destroy the "mymodel" model.
>>> This includes all machines, applications, data and other resources.
>>>
>>> Continue [y/N]? y
>>> ERROR cannot connect to API: model "mymodel" has been removed from the
>>> controller, run 'juju models' and switch to one of them.
>>> There are 6 accessible models on controller "jaas".
>>>
>>> juju models
>>> Controller: jaas
>>>
>>> Model  Cloud/Region   Status Machines  Cores  Access  Last
>>> connection
>>> mymodelaws/eu-west-1  available 5  9  -   never
>>> connected
>>>
>>>
>>>
>>> 2 things in this output, firstly how do I delete the model that seems
>>> stuck?
>>>
>>> secondly what is the 6 accessible models bit talking about?
>>>
>>> Thanks
>>>
>>> Tom
>>>
>>> --
>>> 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: JAAS confusion

[John Meinel]

The 6 accessible models is gone in 2.3 (IIRC), because it was actually just
reflecting some locally cached information about model numbers, but wasn't
actually being kept up to date properly.

I think the inability to remove a model that is half-dead might be fixed
already in 2.3 but has to do with an issue around 2 critical documents that
define a model, and one of them has been removed but not the other, which
leads to a bunch of code that gets a different view of whether the model
exists or not.

A different explanation could be that you create a model with the same name
with a different client and thus its actually the underlying UUID doesn't
exist, but there is a model collision. (Your local client new a model named
'mymodel' with UUID 1234, but you had a different client that deleted that
model and created a new 'mymodel' with UUID 3456, but when you're trying to
'juju destroy-model' we are using the 1234 UUID again. I'm brainstorming,
though, and wouldn't say concretely that it is definitely true.)

John
=:->


On Mon, Oct 9, 2017 at 9:42 PM, Tom Barber  wrote:

> Hello folks
>
> Couple of random questions:
>
> juju destroy-model mymodel
> WARNING! This command will destroy the "mymodel" model.
> This includes all machines, applications, data and other resources.
>
> Continue [y/N]? y
> ERROR cannot connect to API: model "mymodel" has been removed from the
> controller, run 'juju models' and switch to one of them.
> There are 6 accessible models on controller "jaas".
>
> juju models
> Controller: jaas
>
> Model  Cloud/Region   Status Machines  Cores  Access  Last
> connection
> mymodelaws/eu-west-1  available 5  9  -   never
> connected
>
>
>
> 2 things in this output, firstly how do I delete the model that seems
> stuck?
>
> secondly what is the 6 accessible models bit talking about?
>
> Thanks
>
> Tom
>
> --
> 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

JAAS confusion

[Tom Barber]

Hello folks

Couple of random questions:

juju destroy-model mymodel
WARNING! This command will destroy the "mymodel" model.
This includes all machines, applications, data and other resources.

Continue [y/N]? y
ERROR cannot connect to API: model "mymodel" has been removed from the
controller, run 'juju models' and switch to one of them.
There are 6 accessible models on controller "jaas".

juju models
Controller: jaas

Model  Cloud/Region   Status Machines  Cores  Access  Last
connection
mymodelaws/eu-west-1  available 5  9  -   never
connected



2 things in this output, firstly how do I delete the model that seems stuck?

secondly what is the 6 accessible models bit talking about?

Thanks

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