Re: Juju deploy mongodb error!

Hello, This was fixed in 1.25.1. Which version of Juju and MaaS are you using? The root cause is DNS related and this error occurs when the connection to the mongo DB cannot be resolved. In your output it looks like "bootstrap.maas" is not resolving. The fix that landed in 1.25.1 changed the

Review Queue - midonet-api

Hi Folks I spent my morning reviewing the Midonet charms proposed under: https://bugs.launchpad.net/charms/+bug/1453678 I set myself a challenge of managing to run the amulet tests in our egress limited QA cloud; managed to get most of that working with local mirrors of datastax and midonet

Starting a new CI test

I just added a cheaty way of getting started on a new CI test. $ make new-assess name=new_feature With 'new_feature' as the name you want for your test. This generates a new test script, and some unit tests to go along with it, which you can run as normal with: $ make test p=*new_feature* The

gomaasapi moved to github

The gomaasapi project has been moved from launchpad to the juju organisation on github: As part of this, the project is using the standard juju gating, so add the magic string $$merge$$ to a github comment after review to merge. Martin -- Juju-dev mailing

Re: 1st time builder

Usually if there are compile time issues, it's because you haven't run godeps yet. Make sure you've done the steps under this section of the docs: https://github.com/juju/juju/blob/master/CONTRIBUTING.md#godeps go-get by default pulls from the head of every git repo, but to keep our builds

Re: Starting a new CI test

That is amazing and awesome. Thanks, Martin and everyone else who helped with this! Lowering the barrier of entry to writing CI tests can only be a good thing. On Thu, Dec 17, 2015 at 1:00 PM Martin Packman wrote: > I just added a cheaty way of getting started on

1st time builder

I am attempting to build juju for the 1st time using the instructions at https://github.com/juju/juju and appear to have all the dependencies installed. I am using golang 1.5. I have searched this month¹s mailing list archives (juju and juju-dev) and googled the symptoms and got nothing. I am

Re: Charms, layers, and Launchpad

On Fri, Dec 18, 2015 at 9:27 AM Cory Johns wrote: > Andrew, > > It's mentioned at the start of > https://jujucharms.com/docs/stable/authors-charm-building and there is a > PR (https://github.com/juju/docs/pull/746) to rework the existing authors > doc into a developer

Re: Charms, layers, and Launchpad

Andrew, Good point. I opened https://github.com/juju/charm-tools/issues/84 for offline dev support. On Thu, Dec 17, 2015 at 6:33 PM, Andrew Wilkins < andrew.wilk...@canonical.com> wrote: > On Fri, Dec 18, 2015 at 9:27 AM Cory Johns > wrote: > >> Andrew, >> >> It's

Re: Charms, layers, and Launchpad

Not sure if it will work completely offline, but you'll probably want to pull all the layers/interfaces you want into INTERFACE_PATH and LAYER_PATH. If I recall correctly, those are searched first for matches before the index. The pip stuff is a bit harder, but it seems reasonable that we could

Recover from 'Agent is lost'

Hi [manual provider] after rebooting a machine that contained lxc container units, Juju displays 'agent is lost' for those containers h-bigmoo2/0 unknownlost1.24.7 1/lxc/9 agent is lost, sorry! See 'juju status-history h-bigmoo2/0' h-bigmootest/0 unknownlost

答复: Juju deploy mongodb error!

Hi , Andrew McDermott Thanks for your help. The juju version is 1.25.0 and the maas is 1.8.3. I checked I have set the static IP range,but it still can’t pass. But with the https://bugs.launchpad.net/juju-core/+bug/1412621/comments/15,it could complete successfully. That’s strange. Yuanyou

Re: 答复: Juju deploy mongodb error!

Please could you try again but with 1.25.1. https://launchpad.net/juju-core/+milestone/1.25.1 On 17 December 2015 at 12:23, zhangyuanyou wrote: > Hi , Andrew McDermott > >Thanks for your help. > > The juju version is 1.25.0 and the maas is 1.8.3. > > I checked I