Just a heads up that the upgrade issues have been worked out and all of the
JAAS controllers are confirmed to be at 2.2.6. We'll be looking at updating
to 2.3.1 in the near future.
On Mon, Dec 4, 2017 at 1:20 PM Tom Barber wrote:
> Thanks chaps,
>
> I'll try elsewhere.
>
>
> Tom
>
>
> On 04/12/17 18:17, Rick Harding wrote:
>
> Thanks for this Tom, for some reason the controller in the region there
> isn't running 2.2.6, we're looking into it and will try to get it updated
> as soon as possible.
>
> On Mon, Dec 4, 2017 at 9:22 AM Tom Barber wrote:
>
>> mymodel jaasaws/us-east-1 2.2.2unsupported
>>
>>
>> Tom
>>
>>
>> On 04/12/17 14:08, Matthew Williams wrote:
>>
>> Hi Tom,
>>
>> What version of the controller are you using (show in juju status). Is
>> this your own controller or are you using jimm?
>>
>> Thanks
>>
>> Matty
>>
>> On Mon, Dec 4, 2017 at 10:33 AM, Tom Barber wrote:
>>
>>> Hi Casey
>>>
>>> https://asciinema.org/a/qXUZqY5WhCYFUA44l9OILeZWB As you'll see here.
>>> #45 works for me also but #47 fails. I don't think we changed anything
>>> massively but clearly something in there is sad, the problem is that, the
>>> error thrown gives me no indication of where we've messed up.
>>>
>>> On a side note I wanted to grab the zip archive of #45 and #47 and do a
>>> diff to see if it was obvious but both give me a 404 from the charm store.
>>>
>>> juju list-agreements
>>> Term Agreed on
>>> isrg-lets-encrypt/2 2017-04-26 09:43:38 + UTC
>>> canonical/sla-terms/32017-08-31 21:19:16 + UTC
>>> spiculecharms/pdi-terms/12017-11-27 23:24:11 + UTC
>>>
>>> Tom
>>>
>>>
>>> On 04/12/17 02:54, Casey Marshall wrote:
>>>
>>> Tom,
>>> With 2.2.6, I cannot reproduce any problems with deploying your charm.
>>> See https://paste.ubuntu.com/26109617/
>>>
>>> Please send me more information about your installation:
>>>
>>> - How you installed Juju (snap, deb from PPA, compiled from source, etc.)
>>> - Platform information on the machine you're running the Juju client on,
>>> OS, etc. Is it on a physical host, in a VM, in a container?
>>> - What cloud you're trying to deploy into
>>>
>>> If you type `juju list-agreements`, does that show terms you've agreed
>>> to?
>>>
>>> -Casey
>>>
>>> On Sat, Dec 2, 2017 at 4:55 PM, Tom Barber wrote:
>>>
Just as a quick update, I get the same if I deploy the charm directly
and from the charm store ie not in a bundle.
But removing the terms in the metadata.yaml removes the error.
Tom
On 28/11/17 18:36, Stephen Downie wrote:
Thanks for looking into this Casey. The version of Juju I'm running is
2.2.6-xenial-amd64
Spicule Ltd
Tel: 01603 327762
www.spicule.co.uk
On Tue, Nov 28, 2017 at 6:30 PM, Casey Marshall <
casey.marsh...@canonical.com> wrote:
> On Tue, Nov 28, 2017 at 12:09 PM, Tom Barber
> wrote:
>
>> hey Casey
>>
>> if you have no models and try and deploy a bundle with terms it shows
>> you the deploy screen them hangs. if you go back you see the model with 0
>> units deployed.
>>
>> this is a local bundle we were testing, just exported from the gui,
>> Ste can provide it if you need it.
>>
>
> Thanks for clarifying. One last question, what version of Juju was
> used on the command line when trying to deploy the exported bundle?
>
>
>>
>> Tom
>>
>>
>> On 28 Nov 2017 6:00 pm, "Casey Marshall" <
>> casey.marsh...@canonical.com> wrote:
>>
>> On Tue, Nov 28, 2017 at 10:50 AM, Stephen Downie <
>> step...@spicule.co.uk> wrote:
>>
>>> Thanks. I have tried running juju agree spiculecharms/pdi-terms/1
>>> and it states terms already agreed?
>>>
>>> When trying to deploy in the GUI it returns the error message cannot
>>> create bundle: already exists. It appears that it creates the model but
>>> does't actually deploy anything? I know I'm a bit new to this but
>>> something
>>> seems a bit broken.
>>>
>>
>> Is it possible that the model name in the GUI (the drop down in the
>> upper-left of the canvas) matched an already-created model name? You
>> might
>> need to type in a new model name there.
>>
>> Or does this happen for new models with this bundle no matter what?
>>
>> Was this in the GUI in JAAS (jujucharms.com)? Did you try deploying
>> a bundle from the charmstore, or did you try importing a bundle.yaml
>> file?
>>
>>
>>>
>>> Thanks all for your help.
>>>
>>> Spicule Ltd
>>>
>>> Tel: 01603 327762
>>>
>>>
>>>
>>> www.spicule.co.uk
>>>
>>> On Tue, Nov 28, 2017 at 12:33 PM, Tom Barber
>>> wrote:
>>>