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/1
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
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
Hi Tom,
This appears to be a problem with the 2.2.2 controller which has been fixed
in later versions. If you try a different aws region you should get a more
up to date controller and it should work as expected.
e.g. $ juju add-model mymodel aws/eu-west-1
Hope this helps
Matty
On Mon, Dec 4,
mymodel jaas aws/us-east-1 2.2.2 unsupported
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
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 m
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 s
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 runnin
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
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 Ca
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 th
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.
Tom
On 28 Nov 2017 6:0
On Tue, Nov 28, 2017 at 10:50 AM, Stephen Downie
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 th
On Tue, Nov 28, 2017 at 5:59 AM, John Meinel wrote:
> Do you know what terms you need to accept? You should be able to 'juju
> accept termname'.
> The other thing to check is if your local clock time is fairly accurate.
> I believe we filed a bug recently that the term server gives out temporary
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 t
stupid question, but I assume the bundles should handle t&c's better?
On 28 Nov 2017 12:29, "Ales Stimec" wrote:
> Hi,
>
> Could you please try
>juju agree spiculecharms/pdi-terms/1
>
> This is these are the terms that require agreement in order to deploy
> cs:~spiculecharms/pentaho-data-int
Hi,
Could you please try
juju agree spiculecharms/pdi-terms/1
This is these are the terms that require agreement in order to deploy
cs:~spiculecharms/pentaho-data-integration-45.
To get a list of terms i used:
curl
"https://api.jujucharms.com/charmstore/v5/~spiculecharms/pentaho-data-inte
Do you know what terms you need to accept? You should be able to 'juju
accept termname'.
The other thing to check is if your local clock time is fairly accurate.
I believe we filed a bug recently that the term server gives out temporary
auth tokens that are only valid for 1 minute. (and we end up e
Hi
I am trying to deploy a bundle that has a charm that contains terms and
conditions. I am getting the following error message
https://gist.github.com/gizmo693/5a4fc5235da987a4f64e378e1850dd62
Any help would be appreciated.
Thanks
Steve
Spicule Ltd
Tel: 01603 327762
www.spicule.co.uk
--
19 matches
Mail list logo