You're using local charms (./xenial/mongodb) so it's hard to know for sure
exactly what you're deploying without having the full set of files.
If it is the same as the "official" mongodb: https://jujucharms.com/mongodb/
Then it has several bindings that aren't listed in your bundle. Your bundle
On Sat, Feb 4, 2017 at 9:48 AM, Merlijn Sebrechts
wrote:
> Thanks Cory and team!
>
>
> I didn't test my Charm on a public cloud, which meant I had a code path that
> wasn't executed before. I fixed it and used my Charm Developer Program
> Credentials® verify on AWS.
Well this mongodb charm have not changed since trusty. I doubt that binding
have been defined for this charm. So I think mechanism to define a default
binding for the application where binding is not defined in charms.
Also opnfv-promise application does not have any api to consume so here
also
Narinder, so the beta5 includes the container networking changes that are
required to help make sure that Juju stops guessing bindings incorrectly.
If you look at the error messages in those commands you can see a new error
that the beta5 presents:
message: 'unable to setup network: no
Narinder, so the beta5 includes the container networking changes that are
required to help make sure that Juju stops guessing bindings incorrectly.
If you look at the error messages in those commands you can see a new error
that the beta5 presents:
message: 'unable to setup network: no
Here you go.
juju status --format yaml
http://paste.ubuntu.com/23927017/
juju show-machine 0
http://paste.ubuntu.com/23927020/
pastebinit bundles.yaml
http://paste.ubuntu.com/23927027/
Thanks and Regards,
Narinder Gupta (PMP) narinder.gu...@canonical.com
Canonical, Ltd.
And charmbox makes an appearance! Great work merlijin! I'm looking forward
to giving this a spin.
On Fri, Feb 3, 2017 at 8:06 PM Antonio Rosales <
antonio.rosa...@canonical.com> wrote:
>
>
> On Feb 3, 2017 7:08 PM, "Junaid Ali" wrote:
>
> Great. Thanks Merlijn for sharing.
>
Thanks Cory and team!
I didn't test my Charm on a public cloud, which meant I had a code path
that wasn't executed before. I fixed it and used my Charm Developer Program
Credentials® verify on AWS. Mentioning it because those are very useful! :)
I uploaded the next version to the Charm Store;
Narinder, can you share the output of juju status --format=yaml and juju
show-machine 0
On Sat, Feb 4, 2017, 5:15 AM Narinder Gupta
wrote:
> Hi Nicholas,
> I am finding issues when do the deployment. Bundle i used to deploy with
> juju 2.1-beta4 does not get
Narinder, can you share the output of juju status --format=yaml and juju
show-machine 0
On Sat, Feb 4, 2017, 5:15 AM Narinder Gupta
wrote:
> Hi Nicholas,
> I am finding issues when do the deployment. Bundle i used to deploy with
> juju 2.1-beta4 does not get
Hi Nicholas,
I am finding issues when do the deployment. Bundle i used to deploy with
juju 2.1-beta4 does not get deployed with juju-2.1-beta5.
Reason of that is mongodb lxd container still waiting to get machine which
was not the case for juju 2.1-beta4
mongodb/0 waiting
11 matches
Mail list logo