non standard bridge juju failure about conjure-up HOT 10 CLOSED

We're seeing movement on the launchpad bug now with someone actively working it. I'll post updates here when i know more.

from conjure-up.

Thanks for the report, I'll be tracking this fix at https://bugs.launchpad.net/juju-core/+bug/1575676 since we use Juju under the hood. I'll update this bug once that gets fixed.

from conjure-up.

just cranked it up with default bridge in a vmware vm xenial desktop guest and it worked great

from conjure-up.

Awesome! I'll make sure to keep bringing this issue up for the Juju guys to address

from conjure-up.

I'm facing similar problem.

I followed this HowTo https://bayton.org/2016/05/lxd-zfs-and-bridged-networking-on-ubuntu-16-04-lts/ and changed the br0 name to lxdbr0.
LXD runs perfectly with br0 (with external DHCP server), so containers can get an IP in my network and we can connect into it.

With conjure-up openstack and the option "OpenStack with Nova-LXD", Clouds choose "localhost", after a short bootstraping screen then it says my lxdbr0 is not enabled...

from conjure-up.

Its been a limitation for quite a while and it would be great to get an
idea of when it will be fixed

I'm facing similar problem.

I followed this HowTo
https://bayton.org/2016/05/lxd-zfs-and-bridged-networking-on-ubuntu-16-04-lts/
and changed the br0 name to lxdbr0.
LXD runs perfectly with br0 (with external DHCP server), so containers can
get an IP in my network and we can connect into it.

With conjure-up openstack and the option "OpenStack with Nova-LXD", Clouds
choose "localhost", after a short bootstraping screen then it says my
lxdbr0 is not enabled...

[image: 2016-06-04 07 24 14]
https://cloud.githubusercontent.com/assets/51141/15795599/9f5cab58-2a25-11e6-824b-d101e3ae1355.png

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#37 (comment),
or mute
the thread
https://github.com/notifications/unsubscribe/AAbspsK_ZlQQNzWcmRkBnYwLTdyJK1wuks5qILgtgaJpZM4Il5Zz
.

from conjure-up.

Ive pinged the Juju team again to see if we can get this addressed in Juju 2.0.0

from conjure-up.

Seems fixed? Anyone can confirm?
https://bugs.launchpad.net/juju/+bug/1575676
juju/juju#5871

from conjure-up.

I need to follow up with Juju team

from conjure-up.

This seems fixed now after doing the steps in juju/juju#5871, @niccolox can you try this out now? Please re-open if this is not the case.

from conjure-up.