Re: LXD v2.0.0-rc8 does not work with Juju v2.0-beta3

2016-04-07 Thread Reed O'Brien 
np

On Thu, Apr 7, 2016 at 10:31 AM, roger peppe 
wrote:

> On 7 April 2016 at 17:34, Reed O'Brien  wrote:
> >> Do you want to NAT the IPv4 traffic? n
> >
> > You do want to NAT the traffic, unless you have routing explicitly setup.
>
> Ah, thanks. I knew it must be something stupid like that.
> It now bootstraps and works OK, yay! Thanks Reed.
>



-- 
Reed O'Brien
✉ reed.obr...@canonical.com
✆ 415-562-6797
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: LXD v2.0.0-rc8 does not work with Juju v2.0-beta3

2016-04-07 Thread Reed O'Brien 
np

On Thu, Apr 7, 2016 at 10:31 AM, roger peppe 
wrote:

> On 7 April 2016 at 17:34, Reed O'Brien  wrote:
> >> Do you want to NAT the IPv4 traffic? n
> >
> > You do want to NAT the traffic, unless you have routing explicitly setup.
>
> Ah, thanks. I knew it must be something stupid like that.
> It now bootstraps and works OK, yay! Thanks Reed.
>



-- 
Reed O'Brien
✉ reed.obr...@canonical.com
✆ 415-562-6797
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: LXD v2.0.0-rc8 does not work with Juju v2.0-beta3

2016-04-07 Thread roger peppe 
On 7 April 2016 at 17:34, Reed O'Brien  wrote:
>> Do you want to NAT the IPv4 traffic? n
>
> You do want to NAT the traffic, unless you have routing explicitly setup.

Ah, thanks. I knew it must be something stupid like that.
It now bootstraps and works OK, yay! Thanks Reed.

-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: LXD v2.0.0-rc8 does not work with Juju v2.0-beta3

2016-04-07 Thread roger peppe 
On 7 April 2016 at 17:34, Reed O'Brien  wrote:
>> Do you want to NAT the IPv4 traffic? n
>
> You do want to NAT the traffic, unless you have routing explicitly setup.

Ah, thanks. I knew it must be something stupid like that.
It now bootstraps and works OK, yay! Thanks Reed.

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: LXD v2.0.0-rc8 does not work with Juju v2.0-beta3

2016-04-07 Thread Samuel Cozannet 
FYI, had the same issue on IBM hardware, and Antonio helped me get through
it:

* dpkg-reconfigure lxd was necessary to rename the bridge
* Then bootstrap still failed with
2016-04-07 16:35:17 ERROR cmd supercommand.go:448 no registered provider
for "lxd"
ERROR failed to bootstrap model: subprocess encountered error code 1

The fix for that was to add the --upload-tools tag in bootstrap.

So "juju bootstrap deeplearning lxd --upload-tools got me going.

Thanks!
Sam
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: LXD v2.0.0-rc8 does not work with Juju v2.0-beta3

2016-04-07 Thread Reed O'Brien 
> Do you want to NAT the IPv4 traffic? n

You do want to NAT the traffic, unless you have routing explicitly setup.

On Thu, Apr 7, 2016 at 9:17 AM, roger peppe 
wrote:

> OK, thanks, that gets me further. I'd used the netmask from the
> example value in the default /etc/default/lxd-bridge - I assumed they were
> the same format, as the values were.
>
> ## IPv4 netmask (e.g. 255.255.255.0)
>
> Now my bootstrap is stuck further on while installing cpu-checker:
>
> http://paste.ubuntu.com/15673131/
>
> It's been like that for about an hour now. I should probably have
> bootstrapped
> with debug enabled, I guess. It may be a related issue if I mucked
> up the lxd bridge configuration somehow again.
>
>
> On 7 April 2016 at 16:25, Reed O'Brien  wrote:
> > I think you need to enter the CIDR netmask as a bit len, e.g. 24 rather
> than
> > as 255.255.255.0.
> >
> > See
> >
> https://github.com/reedobrien/juju-notes/blob/master/writing-a-ci-test.md
> > and the section on LXD for my personal notes about a working config.
> >
> > HTH,
> > Reed
> >
> > On Thu, Apr 7, 2016 at 8:14 AM, roger peppe 
> > wrote:
> >>
> >> I tried it. I get this error after typing in lots of ipv4 details:
> >>
> >> /var/lib/dpkg/info/lxd.postinst: 8: /var/lib/dpkg/info/lxd.postinst:
> >> arithmetic expression: expecting ')': " 5 - (255.255.255.0 / 8) "
> >>
> >> My full interaction was as follows: http://paste.ubuntu.com/15671384/
> >>
> >>
> >> On 7 April 2016 at 15:57, John Meinel  wrote:
> >> > Did you run dpkg-reconfigure lxd ? That's what I ran once I installed
> >> > the
> >> > new lxd package and it seemed to get things working. Tycho added some
> >> > helpful prompts as part of "juju bootstrap" to point users in the
> right
> >> > direction if LXD looks to be improperly configured.
> >> >
> >> > https://github.com/juju/juju/pull/4984
> >> >
> >> >
> >> > I'm trying to land that now.
> >> >
> >> > John
> >> > =:->
> >> >
> >> > On Apr 7, 2016 6:19 PM, "roger peppe" 
> wrote:
> >> >
> >> > To add to this conversation, I have encountered this issue today
> >> > and have been unable to resolve it so far in the limited time
> >> > I've been able to spend on it.
> >> >
> >> > I'm running on Trusty; I have the new version of lxd and the
> >> > latest version of Juju tip.
> >> >
> >> > In my case, the issue seems to be that my lcdbr0 interface
> >> > has no IPv4 addresses (I've tried fiddling with
> /etc/default/lxd-bridge
> >> > and restarting various things to avail) and that the
> >> > utils.GetAddressForInterface
> >> > function excludes all IPv4 addresses. I'm thinking that it shouldn't
> do
> >> > that,
> >> > but that might not be the only thing that's wrong.
> >> >
> >> >
> >> >
> >> > On 7 April 2016 at 05:10, Pete Vander Giessen 
> wrote:
> >> >> Hi All,
> >> >>
> >> >> Thank you very much for posting this thread. I've been following the
> >> >> "getting started" developer's guide at
> >> >> https://jujucharms.com/docs/devel/getting-started, and this info
> got me
> >> >> unstuck.
> >> >>
> >> >> I figured that I'd mention that, when I ran dpkg-reconfigure, I had
> to
> >> >> create an ipv4 subnet, rather than letting lxd use a proxy, as it
> does
> >> >> by
> >> >> default on a fresh install of Xenial. I'm not sure if it's
> necessarily
> >> >> related to the bridge issue, but I figured I'd be chatty about it in
> >> >> this
> >> >> thread, just in case it helps someone else get themselves unblocked,
> >> >> too
> >> >> (relevant debug logs posted below my sig).
> >> >>
> >> >> Thanks again,
> >> >>
> >> >> ~ PeteVG
> >> >>
> >> >> Logs from my install, before explicitly setting up the subnet:
> >> >>
> >> >> ~$ juju bootstrap --config default-series=xenial lxd-test lxd --debug
> >> >> 2016-04-07 03:51:01 INFO juju.cmd supercommand.go:60 running juju
> >> >> [2.0-beta3
> >> >> gc go1.6]
> >> >> 2016-04-07 03:51:01 INFO cmd cmd.go:141 cloud "lxd" not found, trying
> >> >> as a
> >> >> provider name
> >> >> 2016-04-07 03:51:01 INFO cmd cmd.go:141 no credentials found,
> checking
> >> >> environment
> >> >> 2016-04-07 03:51:01 DEBUG juju.cmd.juju.commands bootstrap.go:363
> >> >> preparing
> >> >> controller with config: map[default-series:xenial type:lxd name:admin
> >> >> uuid:9925cf81-618b-4d50-8f77-b16447c921d8
> >> >> controller-uuid:9925cf81-618b-4d50-8f77-b16447c921d8]
> >> >> 2016-04-07 03:51:01 ERROR cmd supercommand.go:448 invalid config: no
> >> >> addresses match
> >> >>
> >> >>
> >> >> On Wed, Apr 6, 2016 at 5:30 PM Reed O'Brien <
> reed.obr...@canonical.com>
> >> >> wrote:
> >> >>>
> >> >>> The rename works if you haven't removed `lxc1` which removes the
> >> >>> original
> >> >>> `lxcbr0`. If you have you will need to correctly configure another
> >> >>> bridge
> >> >>> as
> >> >>> the new `lxcbr0` that is created has the same configuration as
> >> >>> `lxdbr0`
> >>

Re: LXD v2.0.0-rc8 does not work with Juju v2.0-beta3

2016-04-07 Thread Reed O'Brien 
> Do you want to NAT the IPv4 traffic? n

You do want to NAT the traffic, unless you have routing explicitly setup.

On Thu, Apr 7, 2016 at 9:17 AM, roger peppe 
wrote:

> OK, thanks, that gets me further. I'd used the netmask from the
> example value in the default /etc/default/lxd-bridge - I assumed they were
> the same format, as the values were.
>
> ## IPv4 netmask (e.g. 255.255.255.0)
>
> Now my bootstrap is stuck further on while installing cpu-checker:
>
> http://paste.ubuntu.com/15673131/
>
> It's been like that for about an hour now. I should probably have
> bootstrapped
> with debug enabled, I guess. It may be a related issue if I mucked
> up the lxd bridge configuration somehow again.
>
>
> On 7 April 2016 at 16:25, Reed O'Brien  wrote:
> > I think you need to enter the CIDR netmask as a bit len, e.g. 24 rather
> than
> > as 255.255.255.0.
> >
> > See
> >
> https://github.com/reedobrien/juju-notes/blob/master/writing-a-ci-test.md
> > and the section on LXD for my personal notes about a working config.
> >
> > HTH,
> > Reed
> >
> > On Thu, Apr 7, 2016 at 8:14 AM, roger peppe 
> > wrote:
> >>
> >> I tried it. I get this error after typing in lots of ipv4 details:
> >>
> >> /var/lib/dpkg/info/lxd.postinst: 8: /var/lib/dpkg/info/lxd.postinst:
> >> arithmetic expression: expecting ')': " 5 - (255.255.255.0 / 8) "
> >>
> >> My full interaction was as follows: http://paste.ubuntu.com/15671384/
> >>
> >>
> >> On 7 April 2016 at 15:57, John Meinel  wrote:
> >> > Did you run dpkg-reconfigure lxd ? That's what I ran once I installed
> >> > the
> >> > new lxd package and it seemed to get things working. Tycho added some
> >> > helpful prompts as part of "juju bootstrap" to point users in the
> right
> >> > direction if LXD looks to be improperly configured.
> >> >
> >> > https://github.com/juju/juju/pull/4984
> >> >
> >> >
> >> > I'm trying to land that now.
> >> >
> >> > John
> >> > =:->
> >> >
> >> > On Apr 7, 2016 6:19 PM, "roger peppe" 
> wrote:
> >> >
> >> > To add to this conversation, I have encountered this issue today
> >> > and have been unable to resolve it so far in the limited time
> >> > I've been able to spend on it.
> >> >
> >> > I'm running on Trusty; I have the new version of lxd and the
> >> > latest version of Juju tip.
> >> >
> >> > In my case, the issue seems to be that my lcdbr0 interface
> >> > has no IPv4 addresses (I've tried fiddling with
> /etc/default/lxd-bridge
> >> > and restarting various things to avail) and that the
> >> > utils.GetAddressForInterface
> >> > function excludes all IPv4 addresses. I'm thinking that it shouldn't
> do
> >> > that,
> >> > but that might not be the only thing that's wrong.
> >> >
> >> >
> >> >
> >> > On 7 April 2016 at 05:10, Pete Vander Giessen 
> wrote:
> >> >> Hi All,
> >> >>
> >> >> Thank you very much for posting this thread. I've been following the
> >> >> "getting started" developer's guide at
> >> >> https://jujucharms.com/docs/devel/getting-started, and this info
> got me
> >> >> unstuck.
> >> >>
> >> >> I figured that I'd mention that, when I ran dpkg-reconfigure, I had
> to
> >> >> create an ipv4 subnet, rather than letting lxd use a proxy, as it
> does
> >> >> by
> >> >> default on a fresh install of Xenial. I'm not sure if it's
> necessarily
> >> >> related to the bridge issue, but I figured I'd be chatty about it in
> >> >> this
> >> >> thread, just in case it helps someone else get themselves unblocked,
> >> >> too
> >> >> (relevant debug logs posted below my sig).
> >> >>
> >> >> Thanks again,
> >> >>
> >> >> ~ PeteVG
> >> >>
> >> >> Logs from my install, before explicitly setting up the subnet:
> >> >>
> >> >> ~$ juju bootstrap --config default-series=xenial lxd-test lxd --debug
> >> >> 2016-04-07 03:51:01 INFO juju.cmd supercommand.go:60 running juju
> >> >> [2.0-beta3
> >> >> gc go1.6]
> >> >> 2016-04-07 03:51:01 INFO cmd cmd.go:141 cloud "lxd" not found, trying
> >> >> as a
> >> >> provider name
> >> >> 2016-04-07 03:51:01 INFO cmd cmd.go:141 no credentials found,
> checking
> >> >> environment
> >> >> 2016-04-07 03:51:01 DEBUG juju.cmd.juju.commands bootstrap.go:363
> >> >> preparing
> >> >> controller with config: map[default-series:xenial type:lxd name:admin
> >> >> uuid:9925cf81-618b-4d50-8f77-b16447c921d8
> >> >> controller-uuid:9925cf81-618b-4d50-8f77-b16447c921d8]
> >> >> 2016-04-07 03:51:01 ERROR cmd supercommand.go:448 invalid config: no
> >> >> addresses match
> >> >>
> >> >>
> >> >> On Wed, Apr 6, 2016 at 5:30 PM Reed O'Brien <
> reed.obr...@canonical.com>
> >> >> wrote:
> >> >>>
> >> >>> The rename works if you haven't removed `lxc1` which removes the
> >> >>> original
> >> >>> `lxcbr0`. If you have you will need to correctly configure another
> >> >>> bridge
> >> >>> as
> >> >>> the new `lxcbr0` that is created has the same configuration as
> >> >>> `lxdbr0`
> >>

Re: LXD v2.0.0-rc8 does not work with Juju v2.0-beta3

2016-04-07 Thread roger peppe 
OK, thanks, that gets me further. I'd used the netmask from the
example value in the default /etc/default/lxd-bridge - I assumed they were
the same format, as the values were.

## IPv4 netmask (e.g. 255.255.255.0)

Now my bootstrap is stuck further on while installing cpu-checker:

http://paste.ubuntu.com/15673131/

It's been like that for about an hour now. I should probably have bootstrapped
with debug enabled, I guess. It may be a related issue if I mucked
up the lxd bridge configuration somehow again.


On 7 April 2016 at 16:25, Reed O'Brien  wrote:
> I think you need to enter the CIDR netmask as a bit len, e.g. 24 rather than
> as 255.255.255.0.
>
> See
> https://github.com/reedobrien/juju-notes/blob/master/writing-a-ci-test.md
> and the section on LXD for my personal notes about a working config.
>
> HTH,
> Reed
>
> On Thu, Apr 7, 2016 at 8:14 AM, roger peppe 
> wrote:
>>
>> I tried it. I get this error after typing in lots of ipv4 details:
>>
>> /var/lib/dpkg/info/lxd.postinst: 8: /var/lib/dpkg/info/lxd.postinst:
>> arithmetic expression: expecting ')': " 5 - (255.255.255.0 / 8) "
>>
>> My full interaction was as follows: http://paste.ubuntu.com/15671384/
>>
>>
>> On 7 April 2016 at 15:57, John Meinel  wrote:
>> > Did you run dpkg-reconfigure lxd ? That's what I ran once I installed
>> > the
>> > new lxd package and it seemed to get things working. Tycho added some
>> > helpful prompts as part of "juju bootstrap" to point users in the right
>> > direction if LXD looks to be improperly configured.
>> >
>> > https://github.com/juju/juju/pull/4984
>> >
>> >
>> > I'm trying to land that now.
>> >
>> > John
>> > =:->
>> >
>> > On Apr 7, 2016 6:19 PM, "roger peppe"  wrote:
>> >
>> > To add to this conversation, I have encountered this issue today
>> > and have been unable to resolve it so far in the limited time
>> > I've been able to spend on it.
>> >
>> > I'm running on Trusty; I have the new version of lxd and the
>> > latest version of Juju tip.
>> >
>> > In my case, the issue seems to be that my lcdbr0 interface
>> > has no IPv4 addresses (I've tried fiddling with /etc/default/lxd-bridge
>> > and restarting various things to avail) and that the
>> > utils.GetAddressForInterface
>> > function excludes all IPv4 addresses. I'm thinking that it shouldn't do
>> > that,
>> > but that might not be the only thing that's wrong.
>> >
>> >
>> >
>> > On 7 April 2016 at 05:10, Pete Vander Giessen  wrote:
>> >> Hi All,
>> >>
>> >> Thank you very much for posting this thread. I've been following the
>> >> "getting started" developer's guide at
>> >> https://jujucharms.com/docs/devel/getting-started, and this info got me
>> >> unstuck.
>> >>
>> >> I figured that I'd mention that, when I ran dpkg-reconfigure, I had to
>> >> create an ipv4 subnet, rather than letting lxd use a proxy, as it does
>> >> by
>> >> default on a fresh install of Xenial. I'm not sure if it's necessarily
>> >> related to the bridge issue, but I figured I'd be chatty about it in
>> >> this
>> >> thread, just in case it helps someone else get themselves unblocked,
>> >> too
>> >> (relevant debug logs posted below my sig).
>> >>
>> >> Thanks again,
>> >>
>> >> ~ PeteVG
>> >>
>> >> Logs from my install, before explicitly setting up the subnet:
>> >>
>> >> ~$ juju bootstrap --config default-series=xenial lxd-test lxd --debug
>> >> 2016-04-07 03:51:01 INFO juju.cmd supercommand.go:60 running juju
>> >> [2.0-beta3
>> >> gc go1.6]
>> >> 2016-04-07 03:51:01 INFO cmd cmd.go:141 cloud "lxd" not found, trying
>> >> as a
>> >> provider name
>> >> 2016-04-07 03:51:01 INFO cmd cmd.go:141 no credentials found, checking
>> >> environment
>> >> 2016-04-07 03:51:01 DEBUG juju.cmd.juju.commands bootstrap.go:363
>> >> preparing
>> >> controller with config: map[default-series:xenial type:lxd name:admin
>> >> uuid:9925cf81-618b-4d50-8f77-b16447c921d8
>> >> controller-uuid:9925cf81-618b-4d50-8f77-b16447c921d8]
>> >> 2016-04-07 03:51:01 ERROR cmd supercommand.go:448 invalid config: no
>> >> addresses match
>> >>
>> >>
>> >> On Wed, Apr 6, 2016 at 5:30 PM Reed O'Brien 
>> >> wrote:
>> >>>
>> >>> The rename works if you haven't removed `lxc1` which removes the
>> >>> original
>> >>> `lxcbr0`. If you have you will need to correctly configure another
>> >>> bridge
>> >>> as
>> >>> the new `lxcbr0` that is created has the same configuration as
>> >>> `lxdbr0`
>> >>> if
>> >>> you configured an `lxdbr0`... For me this led to two bridges with the
>> >>> same
>> >>> address info, which didn't work out so slick.
>> >>>
>> >>> Also, you need to `systemctl stop lxd-bridge.service && systemctl
>> >>> restart
>> >>> lxd.service` in the correct order.
>> >>>
>> >>> On Wed, Apr 6, 2016 at 2:22 PM, Andrew McDermott
>> >>>  wrote:
>> 
>>  I think you'll need to `service lxd-bridge restart' in

Re: LXD v2.0.0-rc8 does not work with Juju v2.0-beta3

2016-04-07 Thread roger peppe 
OK, thanks, that gets me further. I'd used the netmask from the
example value in the default /etc/default/lxd-bridge - I assumed they were
the same format, as the values were.

## IPv4 netmask (e.g. 255.255.255.0)

Now my bootstrap is stuck further on while installing cpu-checker:

http://paste.ubuntu.com/15673131/

It's been like that for about an hour now. I should probably have bootstrapped
with debug enabled, I guess. It may be a related issue if I mucked
up the lxd bridge configuration somehow again.


On 7 April 2016 at 16:25, Reed O'Brien  wrote:
> I think you need to enter the CIDR netmask as a bit len, e.g. 24 rather than
> as 255.255.255.0.
>
> See
> https://github.com/reedobrien/juju-notes/blob/master/writing-a-ci-test.md
> and the section on LXD for my personal notes about a working config.
>
> HTH,
> Reed
>
> On Thu, Apr 7, 2016 at 8:14 AM, roger peppe 
> wrote:
>>
>> I tried it. I get this error after typing in lots of ipv4 details:
>>
>> /var/lib/dpkg/info/lxd.postinst: 8: /var/lib/dpkg/info/lxd.postinst:
>> arithmetic expression: expecting ')': " 5 - (255.255.255.0 / 8) "
>>
>> My full interaction was as follows: http://paste.ubuntu.com/15671384/
>>
>>
>> On 7 April 2016 at 15:57, John Meinel  wrote:
>> > Did you run dpkg-reconfigure lxd ? That's what I ran once I installed
>> > the
>> > new lxd package and it seemed to get things working. Tycho added some
>> > helpful prompts as part of "juju bootstrap" to point users in the right
>> > direction if LXD looks to be improperly configured.
>> >
>> > https://github.com/juju/juju/pull/4984
>> >
>> >
>> > I'm trying to land that now.
>> >
>> > John
>> > =:->
>> >
>> > On Apr 7, 2016 6:19 PM, "roger peppe"  wrote:
>> >
>> > To add to this conversation, I have encountered this issue today
>> > and have been unable to resolve it so far in the limited time
>> > I've been able to spend on it.
>> >
>> > I'm running on Trusty; I have the new version of lxd and the
>> > latest version of Juju tip.
>> >
>> > In my case, the issue seems to be that my lcdbr0 interface
>> > has no IPv4 addresses (I've tried fiddling with /etc/default/lxd-bridge
>> > and restarting various things to avail) and that the
>> > utils.GetAddressForInterface
>> > function excludes all IPv4 addresses. I'm thinking that it shouldn't do
>> > that,
>> > but that might not be the only thing that's wrong.
>> >
>> >
>> >
>> > On 7 April 2016 at 05:10, Pete Vander Giessen  wrote:
>> >> Hi All,
>> >>
>> >> Thank you very much for posting this thread. I've been following the
>> >> "getting started" developer's guide at
>> >> https://jujucharms.com/docs/devel/getting-started, and this info got me
>> >> unstuck.
>> >>
>> >> I figured that I'd mention that, when I ran dpkg-reconfigure, I had to
>> >> create an ipv4 subnet, rather than letting lxd use a proxy, as it does
>> >> by
>> >> default on a fresh install of Xenial. I'm not sure if it's necessarily
>> >> related to the bridge issue, but I figured I'd be chatty about it in
>> >> this
>> >> thread, just in case it helps someone else get themselves unblocked,
>> >> too
>> >> (relevant debug logs posted below my sig).
>> >>
>> >> Thanks again,
>> >>
>> >> ~ PeteVG
>> >>
>> >> Logs from my install, before explicitly setting up the subnet:
>> >>
>> >> ~$ juju bootstrap --config default-series=xenial lxd-test lxd --debug
>> >> 2016-04-07 03:51:01 INFO juju.cmd supercommand.go:60 running juju
>> >> [2.0-beta3
>> >> gc go1.6]
>> >> 2016-04-07 03:51:01 INFO cmd cmd.go:141 cloud "lxd" not found, trying
>> >> as a
>> >> provider name
>> >> 2016-04-07 03:51:01 INFO cmd cmd.go:141 no credentials found, checking
>> >> environment
>> >> 2016-04-07 03:51:01 DEBUG juju.cmd.juju.commands bootstrap.go:363
>> >> preparing
>> >> controller with config: map[default-series:xenial type:lxd name:admin
>> >> uuid:9925cf81-618b-4d50-8f77-b16447c921d8
>> >> controller-uuid:9925cf81-618b-4d50-8f77-b16447c921d8]
>> >> 2016-04-07 03:51:01 ERROR cmd supercommand.go:448 invalid config: no
>> >> addresses match
>> >>
>> >>
>> >> On Wed, Apr 6, 2016 at 5:30 PM Reed O'Brien 
>> >> wrote:
>> >>>
>> >>> The rename works if you haven't removed `lxc1` which removes the
>> >>> original
>> >>> `lxcbr0`. If you have you will need to correctly configure another
>> >>> bridge
>> >>> as
>> >>> the new `lxcbr0` that is created has the same configuration as
>> >>> `lxdbr0`
>> >>> if
>> >>> you configured an `lxdbr0`... For me this led to two bridges with the
>> >>> same
>> >>> address info, which didn't work out so slick.
>> >>>
>> >>> Also, you need to `systemctl stop lxd-bridge.service && systemctl
>> >>> restart
>> >>> lxd.service` in the correct order.
>> >>>
>> >>> On Wed, Apr 6, 2016 at 2:22 PM, Andrew McDermott
>> >>>  wrote:
>> 
>>  I think you'll need to `service lxd-bridge restart' in

Re: LXD v2.0.0-rc8 does not work with Juju v2.0-beta3

2016-04-07 Thread Reed O'Brien 
I think you need to enter the CIDR netmask as a bit len, e.g. 24 rather
than as 255.255.255.0.

See
https://github.com/reedobrien/juju-notes/blob/master/writing-a-ci-test.md
and the section on LXD for my personal notes about a working config.

HTH,
Reed

On Thu, Apr 7, 2016 at 8:14 AM, roger peppe 
wrote:

> I tried it. I get this error after typing in lots of ipv4 details:
>
> /var/lib/dpkg/info/lxd.postinst: 8: /var/lib/dpkg/info/lxd.postinst:
> arithmetic expression: expecting ')': " 5 - (255.255.255.0 / 8) "
>
> My full interaction was as follows: http://paste.ubuntu.com/15671384/
>
>
> On 7 April 2016 at 15:57, John Meinel  wrote:
> > Did you run dpkg-reconfigure lxd ? That's what I ran once I installed the
> > new lxd package and it seemed to get things working. Tycho added some
> > helpful prompts as part of "juju bootstrap" to point users in the right
> > direction if LXD looks to be improperly configured.
> >
> > https://github.com/juju/juju/pull/4984
> >
> >
> > I'm trying to land that now.
> >
> > John
> > =:->
> >
> > On Apr 7, 2016 6:19 PM, "roger peppe"  wrote:
> >
> > To add to this conversation, I have encountered this issue today
> > and have been unable to resolve it so far in the limited time
> > I've been able to spend on it.
> >
> > I'm running on Trusty; I have the new version of lxd and the
> > latest version of Juju tip.
> >
> > In my case, the issue seems to be that my lcdbr0 interface
> > has no IPv4 addresses (I've tried fiddling with /etc/default/lxd-bridge
> > and restarting various things to avail) and that the
> > utils.GetAddressForInterface
> > function excludes all IPv4 addresses. I'm thinking that it shouldn't do
> > that,
> > but that might not be the only thing that's wrong.
> >
> >
> >
> > On 7 April 2016 at 05:10, Pete Vander Giessen  wrote:
> >> Hi All,
> >>
> >> Thank you very much for posting this thread. I've been following the
> >> "getting started" developer's guide at
> >> https://jujucharms.com/docs/devel/getting-started, and this info got me
> >> unstuck.
> >>
> >> I figured that I'd mention that, when I ran dpkg-reconfigure, I had to
> >> create an ipv4 subnet, rather than letting lxd use a proxy, as it does
> by
> >> default on a fresh install of Xenial. I'm not sure if it's necessarily
> >> related to the bridge issue, but I figured I'd be chatty about it in
> this
> >> thread, just in case it helps someone else get themselves unblocked, too
> >> (relevant debug logs posted below my sig).
> >>
> >> Thanks again,
> >>
> >> ~ PeteVG
> >>
> >> Logs from my install, before explicitly setting up the subnet:
> >>
> >> ~$ juju bootstrap --config default-series=xenial lxd-test lxd --debug
> >> 2016-04-07 03:51:01 INFO juju.cmd supercommand.go:60 running juju
> >> [2.0-beta3
> >> gc go1.6]
> >> 2016-04-07 03:51:01 INFO cmd cmd.go:141 cloud "lxd" not found, trying
> as a
> >> provider name
> >> 2016-04-07 03:51:01 INFO cmd cmd.go:141 no credentials found, checking
> >> environment
> >> 2016-04-07 03:51:01 DEBUG juju.cmd.juju.commands bootstrap.go:363
> >> preparing
> >> controller with config: map[default-series:xenial type:lxd name:admin
> >> uuid:9925cf81-618b-4d50-8f77-b16447c921d8
> >> controller-uuid:9925cf81-618b-4d50-8f77-b16447c921d8]
> >> 2016-04-07 03:51:01 ERROR cmd supercommand.go:448 invalid config: no
> >> addresses match
> >>
> >>
> >> On Wed, Apr 6, 2016 at 5:30 PM Reed O'Brien 
> >> wrote:
> >>>
> >>> The rename works if you haven't removed `lxc1` which removes the
> original
> >>> `lxcbr0`. If you have you will need to correctly configure another
> bridge
> >>> as
> >>> the new `lxcbr0` that is created has the same configuration as `lxdbr0`
> >>> if
> >>> you configured an `lxdbr0`... For me this led to two bridges with the
> >>> same
> >>> address info, which didn't work out so slick.
> >>>
> >>> Also, you need to `systemctl stop lxd-bridge.service && systemctl
> restart
> >>> lxd.service` in the correct order.
> >>>
> >>> On Wed, Apr 6, 2016 at 2:22 PM, Andrew McDermott
> >>>  wrote:
> 
>  I think you'll need to `service lxd-bridge restart' in either case.
> 
>  On 6 April 2016 at 22:18, Horacio Duran 
>  wrote:
> >
> > yes, that workaround works, also you can change
> /etc/default/lxd-bridge
> > and restart the lxd-bridge service.
> >
> > On Wed, Apr 6, 2016 at 6:12 PM, Casey Marshall
> >  wrote:
> >>
> >> On Wed, Apr 6, 2016 at 2:51 PM, Alexis Bruemmer
> >>  wrote:
> >>>
> >>>
> >>> Hi All,
> >>>
> >>> As recently highlighted in bug
> >>> https://bugs.launchpad.net/bugs/1566589
> >>> the latest LXD will not work with Juju 2.0-beta3.  This is a result
> >>> of LXD
> >>> moving to use a default bridge of lxdbr0 and

Re: LXD v2.0.0-rc8 does not work with Juju v2.0-beta3

2016-04-07 Thread Reed O'Brien 
I think you need to enter the CIDR netmask as a bit len, e.g. 24 rather
than as 255.255.255.0.

See
https://github.com/reedobrien/juju-notes/blob/master/writing-a-ci-test.md
and the section on LXD for my personal notes about a working config.

HTH,
Reed

On Thu, Apr 7, 2016 at 8:14 AM, roger peppe 
wrote:

> I tried it. I get this error after typing in lots of ipv4 details:
>
> /var/lib/dpkg/info/lxd.postinst: 8: /var/lib/dpkg/info/lxd.postinst:
> arithmetic expression: expecting ')': " 5 - (255.255.255.0 / 8) "
>
> My full interaction was as follows: http://paste.ubuntu.com/15671384/
>
>
> On 7 April 2016 at 15:57, John Meinel  wrote:
> > Did you run dpkg-reconfigure lxd ? That's what I ran once I installed the
> > new lxd package and it seemed to get things working. Tycho added some
> > helpful prompts as part of "juju bootstrap" to point users in the right
> > direction if LXD looks to be improperly configured.
> >
> > https://github.com/juju/juju/pull/4984
> >
> >
> > I'm trying to land that now.
> >
> > John
> > =:->
> >
> > On Apr 7, 2016 6:19 PM, "roger peppe"  wrote:
> >
> > To add to this conversation, I have encountered this issue today
> > and have been unable to resolve it so far in the limited time
> > I've been able to spend on it.
> >
> > I'm running on Trusty; I have the new version of lxd and the
> > latest version of Juju tip.
> >
> > In my case, the issue seems to be that my lcdbr0 interface
> > has no IPv4 addresses (I've tried fiddling with /etc/default/lxd-bridge
> > and restarting various things to avail) and that the
> > utils.GetAddressForInterface
> > function excludes all IPv4 addresses. I'm thinking that it shouldn't do
> > that,
> > but that might not be the only thing that's wrong.
> >
> >
> >
> > On 7 April 2016 at 05:10, Pete Vander Giessen  wrote:
> >> Hi All,
> >>
> >> Thank you very much for posting this thread. I've been following the
> >> "getting started" developer's guide at
> >> https://jujucharms.com/docs/devel/getting-started, and this info got me
> >> unstuck.
> >>
> >> I figured that I'd mention that, when I ran dpkg-reconfigure, I had to
> >> create an ipv4 subnet, rather than letting lxd use a proxy, as it does
> by
> >> default on a fresh install of Xenial. I'm not sure if it's necessarily
> >> related to the bridge issue, but I figured I'd be chatty about it in
> this
> >> thread, just in case it helps someone else get themselves unblocked, too
> >> (relevant debug logs posted below my sig).
> >>
> >> Thanks again,
> >>
> >> ~ PeteVG
> >>
> >> Logs from my install, before explicitly setting up the subnet:
> >>
> >> ~$ juju bootstrap --config default-series=xenial lxd-test lxd --debug
> >> 2016-04-07 03:51:01 INFO juju.cmd supercommand.go:60 running juju
> >> [2.0-beta3
> >> gc go1.6]
> >> 2016-04-07 03:51:01 INFO cmd cmd.go:141 cloud "lxd" not found, trying
> as a
> >> provider name
> >> 2016-04-07 03:51:01 INFO cmd cmd.go:141 no credentials found, checking
> >> environment
> >> 2016-04-07 03:51:01 DEBUG juju.cmd.juju.commands bootstrap.go:363
> >> preparing
> >> controller with config: map[default-series:xenial type:lxd name:admin
> >> uuid:9925cf81-618b-4d50-8f77-b16447c921d8
> >> controller-uuid:9925cf81-618b-4d50-8f77-b16447c921d8]
> >> 2016-04-07 03:51:01 ERROR cmd supercommand.go:448 invalid config: no
> >> addresses match
> >>
> >>
> >> On Wed, Apr 6, 2016 at 5:30 PM Reed O'Brien 
> >> wrote:
> >>>
> >>> The rename works if you haven't removed `lxc1` which removes the
> original
> >>> `lxcbr0`. If you have you will need to correctly configure another
> bridge
> >>> as
> >>> the new `lxcbr0` that is created has the same configuration as `lxdbr0`
> >>> if
> >>> you configured an `lxdbr0`... For me this led to two bridges with the
> >>> same
> >>> address info, which didn't work out so slick.
> >>>
> >>> Also, you need to `systemctl stop lxd-bridge.service && systemctl
> restart
> >>> lxd.service` in the correct order.
> >>>
> >>> On Wed, Apr 6, 2016 at 2:22 PM, Andrew McDermott
> >>>  wrote:
> 
>  I think you'll need to `service lxd-bridge restart' in either case.
> 
>  On 6 April 2016 at 22:18, Horacio Duran 
>  wrote:
> >
> > yes, that workaround works, also you can change
> /etc/default/lxd-bridge
> > and restart the lxd-bridge service.
> >
> > On Wed, Apr 6, 2016 at 6:12 PM, Casey Marshall
> >  wrote:
> >>
> >> On Wed, Apr 6, 2016 at 2:51 PM, Alexis Bruemmer
> >>  wrote:
> >>>
> >>>
> >>> Hi All,
> >>>
> >>> As recently highlighted in bug
> >>> https://bugs.launchpad.net/bugs/1566589
> >>> the latest LXD will not work with Juju 2.0-beta3.  This is a result
> >>> of LXD
> >>> moving to use a default bridge of lxdbr0 and

Re: LXD v2.0.0-rc8 does not work with Juju v2.0-beta3

2016-04-07 Thread roger peppe 
I tried it. I get this error after typing in lots of ipv4 details:

/var/lib/dpkg/info/lxd.postinst: 8: /var/lib/dpkg/info/lxd.postinst:
arithmetic expression: expecting ')': " 5 - (255.255.255.0 / 8) "

My full interaction was as follows: http://paste.ubuntu.com/15671384/


On 7 April 2016 at 15:57, John Meinel  wrote:
> Did you run dpkg-reconfigure lxd ? That's what I ran once I installed the
> new lxd package and it seemed to get things working. Tycho added some
> helpful prompts as part of "juju bootstrap" to point users in the right
> direction if LXD looks to be improperly configured.
>
> https://github.com/juju/juju/pull/4984
>
>
> I'm trying to land that now.
>
> John
> =:->
>
> On Apr 7, 2016 6:19 PM, "roger peppe"  wrote:
>
> To add to this conversation, I have encountered this issue today
> and have been unable to resolve it so far in the limited time
> I've been able to spend on it.
>
> I'm running on Trusty; I have the new version of lxd and the
> latest version of Juju tip.
>
> In my case, the issue seems to be that my lcdbr0 interface
> has no IPv4 addresses (I've tried fiddling with /etc/default/lxd-bridge
> and restarting various things to avail) and that the
> utils.GetAddressForInterface
> function excludes all IPv4 addresses. I'm thinking that it shouldn't do
> that,
> but that might not be the only thing that's wrong.
>
>
>
> On 7 April 2016 at 05:10, Pete Vander Giessen  wrote:
>> Hi All,
>>
>> Thank you very much for posting this thread. I've been following the
>> "getting started" developer's guide at
>> https://jujucharms.com/docs/devel/getting-started, and this info got me
>> unstuck.
>>
>> I figured that I'd mention that, when I ran dpkg-reconfigure, I had to
>> create an ipv4 subnet, rather than letting lxd use a proxy, as it does by
>> default on a fresh install of Xenial. I'm not sure if it's necessarily
>> related to the bridge issue, but I figured I'd be chatty about it in this
>> thread, just in case it helps someone else get themselves unblocked, too
>> (relevant debug logs posted below my sig).
>>
>> Thanks again,
>>
>> ~ PeteVG
>>
>> Logs from my install, before explicitly setting up the subnet:
>>
>> ~$ juju bootstrap --config default-series=xenial lxd-test lxd --debug
>> 2016-04-07 03:51:01 INFO juju.cmd supercommand.go:60 running juju
>> [2.0-beta3
>> gc go1.6]
>> 2016-04-07 03:51:01 INFO cmd cmd.go:141 cloud "lxd" not found, trying as a
>> provider name
>> 2016-04-07 03:51:01 INFO cmd cmd.go:141 no credentials found, checking
>> environment
>> 2016-04-07 03:51:01 DEBUG juju.cmd.juju.commands bootstrap.go:363
>> preparing
>> controller with config: map[default-series:xenial type:lxd name:admin
>> uuid:9925cf81-618b-4d50-8f77-b16447c921d8
>> controller-uuid:9925cf81-618b-4d50-8f77-b16447c921d8]
>> 2016-04-07 03:51:01 ERROR cmd supercommand.go:448 invalid config: no
>> addresses match
>>
>>
>> On Wed, Apr 6, 2016 at 5:30 PM Reed O'Brien 
>> wrote:
>>>
>>> The rename works if you haven't removed `lxc1` which removes the original
>>> `lxcbr0`. If you have you will need to correctly configure another bridge
>>> as
>>> the new `lxcbr0` that is created has the same configuration as `lxdbr0`
>>> if
>>> you configured an `lxdbr0`... For me this led to two bridges with the
>>> same
>>> address info, which didn't work out so slick.
>>>
>>> Also, you need to `systemctl stop lxd-bridge.service && systemctl restart
>>> lxd.service` in the correct order.
>>>
>>> On Wed, Apr 6, 2016 at 2:22 PM, Andrew McDermott
>>>  wrote:

 I think you'll need to `service lxd-bridge restart' in either case.

 On 6 April 2016 at 22:18, Horacio Duran 
 wrote:
>
> yes, that workaround works, also you can change /etc/default/lxd-bridge
> and restart the lxd-bridge service.
>
> On Wed, Apr 6, 2016 at 6:12 PM, Casey Marshall
>  wrote:
>>
>> On Wed, Apr 6, 2016 at 2:51 PM, Alexis Bruemmer
>>  wrote:
>>>
>>>
>>> Hi All,
>>>
>>> As recently highlighted in bug
>>> https://bugs.launchpad.net/bugs/1566589
>>> the latest LXD will not work with Juju 2.0-beta3.  This is a result
>>> of LXD
>>> moving to use a default bridge of lxdbr0 and Juju expecting lxcbr0.
>>> Thanks
>>> to the heads up and help from the LXD team there is a fix for this in
>>> Juju
>>> master that will be available in the release next week.  However,
>>> until then
>>> Juju 2.0-beta3 will not work with the latest LXD (v2.0.0-rc8).
>>
>>
>> If you `dpkg-reconfigure lxd` and name the bridge "lxcbr0", does this
>> work for beta3? I've been able to bootstrap with latest LXD and
>> current Juju
>> master (beta4) by configuring LXD this way.
>>
>>>
>>>
>>> Alexis
>>>
>>> --

Re: LXD v2.0.0-rc8 does not work with Juju v2.0-beta3

2016-04-07 Thread roger peppe 
I tried it. I get this error after typing in lots of ipv4 details:

/var/lib/dpkg/info/lxd.postinst: 8: /var/lib/dpkg/info/lxd.postinst:
arithmetic expression: expecting ')': " 5 - (255.255.255.0 / 8) "

My full interaction was as follows: http://paste.ubuntu.com/15671384/


On 7 April 2016 at 15:57, John Meinel  wrote:
> Did you run dpkg-reconfigure lxd ? That's what I ran once I installed the
> new lxd package and it seemed to get things working. Tycho added some
> helpful prompts as part of "juju bootstrap" to point users in the right
> direction if LXD looks to be improperly configured.
>
> https://github.com/juju/juju/pull/4984
>
>
> I'm trying to land that now.
>
> John
> =:->
>
> On Apr 7, 2016 6:19 PM, "roger peppe"  wrote:
>
> To add to this conversation, I have encountered this issue today
> and have been unable to resolve it so far in the limited time
> I've been able to spend on it.
>
> I'm running on Trusty; I have the new version of lxd and the
> latest version of Juju tip.
>
> In my case, the issue seems to be that my lcdbr0 interface
> has no IPv4 addresses (I've tried fiddling with /etc/default/lxd-bridge
> and restarting various things to avail) and that the
> utils.GetAddressForInterface
> function excludes all IPv4 addresses. I'm thinking that it shouldn't do
> that,
> but that might not be the only thing that's wrong.
>
>
>
> On 7 April 2016 at 05:10, Pete Vander Giessen  wrote:
>> Hi All,
>>
>> Thank you very much for posting this thread. I've been following the
>> "getting started" developer's guide at
>> https://jujucharms.com/docs/devel/getting-started, and this info got me
>> unstuck.
>>
>> I figured that I'd mention that, when I ran dpkg-reconfigure, I had to
>> create an ipv4 subnet, rather than letting lxd use a proxy, as it does by
>> default on a fresh install of Xenial. I'm not sure if it's necessarily
>> related to the bridge issue, but I figured I'd be chatty about it in this
>> thread, just in case it helps someone else get themselves unblocked, too
>> (relevant debug logs posted below my sig).
>>
>> Thanks again,
>>
>> ~ PeteVG
>>
>> Logs from my install, before explicitly setting up the subnet:
>>
>> ~$ juju bootstrap --config default-series=xenial lxd-test lxd --debug
>> 2016-04-07 03:51:01 INFO juju.cmd supercommand.go:60 running juju
>> [2.0-beta3
>> gc go1.6]
>> 2016-04-07 03:51:01 INFO cmd cmd.go:141 cloud "lxd" not found, trying as a
>> provider name
>> 2016-04-07 03:51:01 INFO cmd cmd.go:141 no credentials found, checking
>> environment
>> 2016-04-07 03:51:01 DEBUG juju.cmd.juju.commands bootstrap.go:363
>> preparing
>> controller with config: map[default-series:xenial type:lxd name:admin
>> uuid:9925cf81-618b-4d50-8f77-b16447c921d8
>> controller-uuid:9925cf81-618b-4d50-8f77-b16447c921d8]
>> 2016-04-07 03:51:01 ERROR cmd supercommand.go:448 invalid config: no
>> addresses match
>>
>>
>> On Wed, Apr 6, 2016 at 5:30 PM Reed O'Brien 
>> wrote:
>>>
>>> The rename works if you haven't removed `lxc1` which removes the original
>>> `lxcbr0`. If you have you will need to correctly configure another bridge
>>> as
>>> the new `lxcbr0` that is created has the same configuration as `lxdbr0`
>>> if
>>> you configured an `lxdbr0`... For me this led to two bridges with the
>>> same
>>> address info, which didn't work out so slick.
>>>
>>> Also, you need to `systemctl stop lxd-bridge.service && systemctl restart
>>> lxd.service` in the correct order.
>>>
>>> On Wed, Apr 6, 2016 at 2:22 PM, Andrew McDermott
>>>  wrote:

 I think you'll need to `service lxd-bridge restart' in either case.

 On 6 April 2016 at 22:18, Horacio Duran 
 wrote:
>
> yes, that workaround works, also you can change /etc/default/lxd-bridge
> and restart the lxd-bridge service.
>
> On Wed, Apr 6, 2016 at 6:12 PM, Casey Marshall
>  wrote:
>>
>> On Wed, Apr 6, 2016 at 2:51 PM, Alexis Bruemmer
>>  wrote:
>>>
>>>
>>> Hi All,
>>>
>>> As recently highlighted in bug
>>> https://bugs.launchpad.net/bugs/1566589
>>> the latest LXD will not work with Juju 2.0-beta3.  This is a result
>>> of LXD
>>> moving to use a default bridge of lxdbr0 and Juju expecting lxcbr0.
>>> Thanks
>>> to the heads up and help from the LXD team there is a fix for this in
>>> Juju
>>> master that will be available in the release next week.  However,
>>> until then
>>> Juju 2.0-beta3 will not work with the latest LXD (v2.0.0-rc8).
>>
>>
>> If you `dpkg-reconfigure lxd` and name the bridge "lxcbr0", does this
>> work for beta3? I've been able to bootstrap with latest LXD and
>> current Juju
>> master (beta4) by configuring LXD this way.
>>
>>>
>>>
>>> Alexis
>>>
>>> --

Re: LXD v2.0.0-rc8 does not work with Juju v2.0-beta3

2016-04-07 Thread John Meinel 
Did you run dpkg-reconfigure lxd ? That's what I ran once I installed the
new lxd package and it seemed to get things working. Tycho added some
helpful prompts as part of "juju bootstrap" to point users in the right
direction if LXD looks to be improperly configured.

https://github.com/juju/juju/pull/4984


I'm trying to land that now.

John
=:->
On Apr 7, 2016 6:19 PM, "roger peppe"  wrote:

To add to this conversation, I have encountered this issue today
and have been unable to resolve it so far in the limited time
I've been able to spend on it.

I'm running on Trusty; I have the new version of lxd and the
latest version of Juju tip.

In my case, the issue seems to be that my lcdbr0 interface
has no IPv4 addresses (I've tried fiddling with /etc/default/lxd-bridge
and restarting various things to avail) and that the
utils.GetAddressForInterface
function excludes all IPv4 addresses. I'm thinking that it shouldn't do
that,
but that might not be the only thing that's wrong.



On 7 April 2016 at 05:10, Pete Vander Giessen  wrote:
> Hi All,
>
> Thank you very much for posting this thread. I've been following the
> "getting started" developer's guide at
> https://jujucharms.com/docs/devel/getting-started, and this info got me
> unstuck.
>
> I figured that I'd mention that, when I ran dpkg-reconfigure, I had to
> create an ipv4 subnet, rather than letting lxd use a proxy, as it does by
> default on a fresh install of Xenial. I'm not sure if it's necessarily
> related to the bridge issue, but I figured I'd be chatty about it in this
> thread, just in case it helps someone else get themselves unblocked, too
> (relevant debug logs posted below my sig).
>
> Thanks again,
>
> ~ PeteVG
>
> Logs from my install, before explicitly setting up the subnet:
>
> ~$ juju bootstrap --config default-series=xenial lxd-test lxd --debug
> 2016-04-07 03:51:01 INFO juju.cmd supercommand.go:60 running juju
[2.0-beta3
> gc go1.6]
> 2016-04-07 03:51:01 INFO cmd cmd.go:141 cloud "lxd" not found, trying as a
> provider name
> 2016-04-07 03:51:01 INFO cmd cmd.go:141 no credentials found, checking
> environment
> 2016-04-07 03:51:01 DEBUG juju.cmd.juju.commands bootstrap.go:363
preparing
> controller with config: map[default-series:xenial type:lxd name:admin
> uuid:9925cf81-618b-4d50-8f77-b16447c921d8
> controller-uuid:9925cf81-618b-4d50-8f77-b16447c921d8]
> 2016-04-07 03:51:01 ERROR cmd supercommand.go:448 invalid config: no
> addresses match
>
>
> On Wed, Apr 6, 2016 at 5:30 PM Reed O'Brien 
> wrote:
>>
>> The rename works if you haven't removed `lxc1` which removes the original
>> `lxcbr0`. If you have you will need to correctly configure another
bridge as
>> the new `lxcbr0` that is created has the same configuration as `lxdbr0`
if
>> you configured an `lxdbr0`... For me this led to two bridges with the
same
>> address info, which didn't work out so slick.
>>
>> Also, you need to `systemctl stop lxd-bridge.service && systemctl restart
>> lxd.service` in the correct order.
>>
>> On Wed, Apr 6, 2016 at 2:22 PM, Andrew McDermott
>>  wrote:
>>>
>>> I think you'll need to `service lxd-bridge restart' in either case.
>>>
>>> On 6 April 2016 at 22:18, Horacio Duran 
>>> wrote:

 yes, that workaround works, also you can change /etc/default/lxd-bridge
 and restart the lxd-bridge service.

 On Wed, Apr 6, 2016 at 6:12 PM, Casey Marshall
  wrote:
>
> On Wed, Apr 6, 2016 at 2:51 PM, Alexis Bruemmer
>  wrote:
>>
>>
>> Hi All,
>>
>> As recently highlighted in bug
https://bugs.launchpad.net/bugs/1566589
>> the latest LXD will not work with Juju 2.0-beta3.  This is a result
of LXD
>> moving to use a default bridge of lxdbr0 and Juju expecting lxcbr0.
Thanks
>> to the heads up and help from the LXD team there is a fix for this
in Juju
>> master that will be available in the release next week.  However,
until then
>> Juju 2.0-beta3 will not work with the latest LXD (v2.0.0-rc8).
>
>
> If you `dpkg-reconfigure lxd` and name the bridge "lxcbr0", does this
> work for beta3? I've been able to bootstrap with latest LXD and
current Juju
> master (beta4) by configuring LXD this way.
>
>>
>>
>> Alexis
>>
>> --
>> Alexis Bruemmer
>> Juju Core Manager, Canonical Ltd.
>> (503) 686-5018
>> alexis.bruem...@canonical.com
>>
>> --
>> Juju mailing list
>> Juju@lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju
>>
>
>
> --
> Juju-dev mailing list
> juju-...@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>


 --
 Juju-dev mailing list

Re: LXD v2.0.0-rc8 does not work with Juju v2.0-beta3

2016-04-07 Thread John Meinel 
Did you run dpkg-reconfigure lxd ? That's what I ran once I installed the
new lxd package and it seemed to get things working. Tycho added some
helpful prompts as part of "juju bootstrap" to point users in the right
direction if LXD looks to be improperly configured.

https://github.com/juju/juju/pull/4984


I'm trying to land that now.

John
=:->
On Apr 7, 2016 6:19 PM, "roger peppe"  wrote:

To add to this conversation, I have encountered this issue today
and have been unable to resolve it so far in the limited time
I've been able to spend on it.

I'm running on Trusty; I have the new version of lxd and the
latest version of Juju tip.

In my case, the issue seems to be that my lcdbr0 interface
has no IPv4 addresses (I've tried fiddling with /etc/default/lxd-bridge
and restarting various things to avail) and that the
utils.GetAddressForInterface
function excludes all IPv4 addresses. I'm thinking that it shouldn't do
that,
but that might not be the only thing that's wrong.



On 7 April 2016 at 05:10, Pete Vander Giessen  wrote:
> Hi All,
>
> Thank you very much for posting this thread. I've been following the
> "getting started" developer's guide at
> https://jujucharms.com/docs/devel/getting-started, and this info got me
> unstuck.
>
> I figured that I'd mention that, when I ran dpkg-reconfigure, I had to
> create an ipv4 subnet, rather than letting lxd use a proxy, as it does by
> default on a fresh install of Xenial. I'm not sure if it's necessarily
> related to the bridge issue, but I figured I'd be chatty about it in this
> thread, just in case it helps someone else get themselves unblocked, too
> (relevant debug logs posted below my sig).
>
> Thanks again,
>
> ~ PeteVG
>
> Logs from my install, before explicitly setting up the subnet:
>
> ~$ juju bootstrap --config default-series=xenial lxd-test lxd --debug
> 2016-04-07 03:51:01 INFO juju.cmd supercommand.go:60 running juju
[2.0-beta3
> gc go1.6]
> 2016-04-07 03:51:01 INFO cmd cmd.go:141 cloud "lxd" not found, trying as a
> provider name
> 2016-04-07 03:51:01 INFO cmd cmd.go:141 no credentials found, checking
> environment
> 2016-04-07 03:51:01 DEBUG juju.cmd.juju.commands bootstrap.go:363
preparing
> controller with config: map[default-series:xenial type:lxd name:admin
> uuid:9925cf81-618b-4d50-8f77-b16447c921d8
> controller-uuid:9925cf81-618b-4d50-8f77-b16447c921d8]
> 2016-04-07 03:51:01 ERROR cmd supercommand.go:448 invalid config: no
> addresses match
>
>
> On Wed, Apr 6, 2016 at 5:30 PM Reed O'Brien 
> wrote:
>>
>> The rename works if you haven't removed `lxc1` which removes the original
>> `lxcbr0`. If you have you will need to correctly configure another
bridge as
>> the new `lxcbr0` that is created has the same configuration as `lxdbr0`
if
>> you configured an `lxdbr0`... For me this led to two bridges with the
same
>> address info, which didn't work out so slick.
>>
>> Also, you need to `systemctl stop lxd-bridge.service && systemctl restart
>> lxd.service` in the correct order.
>>
>> On Wed, Apr 6, 2016 at 2:22 PM, Andrew McDermott
>>  wrote:
>>>
>>> I think you'll need to `service lxd-bridge restart' in either case.
>>>
>>> On 6 April 2016 at 22:18, Horacio Duran 
>>> wrote:

 yes, that workaround works, also you can change /etc/default/lxd-bridge
 and restart the lxd-bridge service.

 On Wed, Apr 6, 2016 at 6:12 PM, Casey Marshall
  wrote:
>
> On Wed, Apr 6, 2016 at 2:51 PM, Alexis Bruemmer
>  wrote:
>>
>>
>> Hi All,
>>
>> As recently highlighted in bug
https://bugs.launchpad.net/bugs/1566589
>> the latest LXD will not work with Juju 2.0-beta3.  This is a result
of LXD
>> moving to use a default bridge of lxdbr0 and Juju expecting lxcbr0.
Thanks
>> to the heads up and help from the LXD team there is a fix for this
in Juju
>> master that will be available in the release next week.  However,
until then
>> Juju 2.0-beta3 will not work with the latest LXD (v2.0.0-rc8).
>
>
> If you `dpkg-reconfigure lxd` and name the bridge "lxcbr0", does this
> work for beta3? I've been able to bootstrap with latest LXD and
current Juju
> master (beta4) by configuring LXD this way.
>
>>
>>
>> Alexis
>>
>> --
>> Alexis Bruemmer
>> Juju Core Manager, Canonical Ltd.
>> (503) 686-5018
>> alexis.bruem...@canonical.com
>>
>> --
>> Juju mailing list
>> j...@lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju
>>
>
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>


 --
 Juju-dev mailing list

Re: LXD v2.0.0-rc8 does not work with Juju v2.0-beta3

2016-04-07 Thread roger peppe 
To add to this conversation, I have encountered this issue today
and have been unable to resolve it so far in the limited time
I've been able to spend on it.

I'm running on Trusty; I have the new version of lxd and the
latest version of Juju tip.

In my case, the issue seems to be that my lcdbr0 interface
has no IPv4 addresses (I've tried fiddling with /etc/default/lxd-bridge
and restarting various things to avail) and that the
utils.GetAddressForInterface
function excludes all IPv4 addresses. I'm thinking that it shouldn't do that,
but that might not be the only thing that's wrong.



On 7 April 2016 at 05:10, Pete Vander Giessen  wrote:
> Hi All,
>
> Thank you very much for posting this thread. I've been following the
> "getting started" developer's guide at
> https://jujucharms.com/docs/devel/getting-started, and this info got me
> unstuck.
>
> I figured that I'd mention that, when I ran dpkg-reconfigure, I had to
> create an ipv4 subnet, rather than letting lxd use a proxy, as it does by
> default on a fresh install of Xenial. I'm not sure if it's necessarily
> related to the bridge issue, but I figured I'd be chatty about it in this
> thread, just in case it helps someone else get themselves unblocked, too
> (relevant debug logs posted below my sig).
>
> Thanks again,
>
> ~ PeteVG
>
> Logs from my install, before explicitly setting up the subnet:
>
> ~$ juju bootstrap --config default-series=xenial lxd-test lxd --debug
> 2016-04-07 03:51:01 INFO juju.cmd supercommand.go:60 running juju [2.0-beta3
> gc go1.6]
> 2016-04-07 03:51:01 INFO cmd cmd.go:141 cloud "lxd" not found, trying as a
> provider name
> 2016-04-07 03:51:01 INFO cmd cmd.go:141 no credentials found, checking
> environment
> 2016-04-07 03:51:01 DEBUG juju.cmd.juju.commands bootstrap.go:363 preparing
> controller with config: map[default-series:xenial type:lxd name:admin
> uuid:9925cf81-618b-4d50-8f77-b16447c921d8
> controller-uuid:9925cf81-618b-4d50-8f77-b16447c921d8]
> 2016-04-07 03:51:01 ERROR cmd supercommand.go:448 invalid config: no
> addresses match
>
>
> On Wed, Apr 6, 2016 at 5:30 PM Reed O'Brien 
> wrote:
>>
>> The rename works if you haven't removed `lxc1` which removes the original
>> `lxcbr0`. If you have you will need to correctly configure another bridge as
>> the new `lxcbr0` that is created has the same configuration as `lxdbr0` if
>> you configured an `lxdbr0`... For me this led to two bridges with the same
>> address info, which didn't work out so slick.
>>
>> Also, you need to `systemctl stop lxd-bridge.service && systemctl restart
>> lxd.service` in the correct order.
>>
>> On Wed, Apr 6, 2016 at 2:22 PM, Andrew McDermott
>>  wrote:
>>>
>>> I think you'll need to `service lxd-bridge restart' in either case.
>>>
>>> On 6 April 2016 at 22:18, Horacio Duran 
>>> wrote:

 yes, that workaround works, also you can change /etc/default/lxd-bridge
 and restart the lxd-bridge service.

 On Wed, Apr 6, 2016 at 6:12 PM, Casey Marshall
  wrote:
>
> On Wed, Apr 6, 2016 at 2:51 PM, Alexis Bruemmer
>  wrote:
>>
>>
>> Hi All,
>>
>> As recently highlighted in bug https://bugs.launchpad.net/bugs/1566589
>> the latest LXD will not work with Juju 2.0-beta3.  This is a result of 
>> LXD
>> moving to use a default bridge of lxdbr0 and Juju expecting lxcbr0.  
>> Thanks
>> to the heads up and help from the LXD team there is a fix for this in 
>> Juju
>> master that will be available in the release next week.  However, until 
>> then
>> Juju 2.0-beta3 will not work with the latest LXD (v2.0.0-rc8).
>
>
> If you `dpkg-reconfigure lxd` and name the bridge "lxcbr0", does this
> work for beta3? I've been able to bootstrap with latest LXD and current 
> Juju
> master (beta4) by configuring LXD this way.
>
>>
>>
>> Alexis
>>
>> --
>> Alexis Bruemmer
>> Juju Core Manager, Canonical Ltd.
>> (503) 686-5018
>> alexis.bruem...@canonical.com
>>
>> --
>> Juju mailing list
>> Juju@lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju
>>
>
>
> --
> Juju-dev mailing list
> juju-...@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>


 --
 Juju-dev mailing list
 juju-...@lists.ubuntu.com
 Modify settings or unsubscribe at:
 https://lists.ubuntu.com/mailman/listinfo/juju-dev

>>>
>>>
>>>
>>> --
>>> Andrew McDermott 
>>> Juju Core Sapphire team 
>>>
>>> --
>>> Juju-dev mailing list
>>> juju-...@lists.ubuntu.com
>>> Modify settings or unsubscribe at:
>>>

Re: LXD v2.0.0-rc8 does not work with Juju v2.0-beta3

2016-04-07 Thread roger peppe 
To add to this conversation, I have encountered this issue today
and have been unable to resolve it so far in the limited time
I've been able to spend on it.

I'm running on Trusty; I have the new version of lxd and the
latest version of Juju tip.

In my case, the issue seems to be that my lcdbr0 interface
has no IPv4 addresses (I've tried fiddling with /etc/default/lxd-bridge
and restarting various things to avail) and that the
utils.GetAddressForInterface
function excludes all IPv4 addresses. I'm thinking that it shouldn't do that,
but that might not be the only thing that's wrong.



On 7 April 2016 at 05:10, Pete Vander Giessen  wrote:
> Hi All,
>
> Thank you very much for posting this thread. I've been following the
> "getting started" developer's guide at
> https://jujucharms.com/docs/devel/getting-started, and this info got me
> unstuck.
>
> I figured that I'd mention that, when I ran dpkg-reconfigure, I had to
> create an ipv4 subnet, rather than letting lxd use a proxy, as it does by
> default on a fresh install of Xenial. I'm not sure if it's necessarily
> related to the bridge issue, but I figured I'd be chatty about it in this
> thread, just in case it helps someone else get themselves unblocked, too
> (relevant debug logs posted below my sig).
>
> Thanks again,
>
> ~ PeteVG
>
> Logs from my install, before explicitly setting up the subnet:
>
> ~$ juju bootstrap --config default-series=xenial lxd-test lxd --debug
> 2016-04-07 03:51:01 INFO juju.cmd supercommand.go:60 running juju [2.0-beta3
> gc go1.6]
> 2016-04-07 03:51:01 INFO cmd cmd.go:141 cloud "lxd" not found, trying as a
> provider name
> 2016-04-07 03:51:01 INFO cmd cmd.go:141 no credentials found, checking
> environment
> 2016-04-07 03:51:01 DEBUG juju.cmd.juju.commands bootstrap.go:363 preparing
> controller with config: map[default-series:xenial type:lxd name:admin
> uuid:9925cf81-618b-4d50-8f77-b16447c921d8
> controller-uuid:9925cf81-618b-4d50-8f77-b16447c921d8]
> 2016-04-07 03:51:01 ERROR cmd supercommand.go:448 invalid config: no
> addresses match
>
>
> On Wed, Apr 6, 2016 at 5:30 PM Reed O'Brien 
> wrote:
>>
>> The rename works if you haven't removed `lxc1` which removes the original
>> `lxcbr0`. If you have you will need to correctly configure another bridge as
>> the new `lxcbr0` that is created has the same configuration as `lxdbr0` if
>> you configured an `lxdbr0`... For me this led to two bridges with the same
>> address info, which didn't work out so slick.
>>
>> Also, you need to `systemctl stop lxd-bridge.service && systemctl restart
>> lxd.service` in the correct order.
>>
>> On Wed, Apr 6, 2016 at 2:22 PM, Andrew McDermott
>>  wrote:
>>>
>>> I think you'll need to `service lxd-bridge restart' in either case.
>>>
>>> On 6 April 2016 at 22:18, Horacio Duran 
>>> wrote:

 yes, that workaround works, also you can change /etc/default/lxd-bridge
 and restart the lxd-bridge service.

 On Wed, Apr 6, 2016 at 6:12 PM, Casey Marshall
  wrote:
>
> On Wed, Apr 6, 2016 at 2:51 PM, Alexis Bruemmer
>  wrote:
>>
>>
>> Hi All,
>>
>> As recently highlighted in bug https://bugs.launchpad.net/bugs/1566589
>> the latest LXD will not work with Juju 2.0-beta3.  This is a result of 
>> LXD
>> moving to use a default bridge of lxdbr0 and Juju expecting lxcbr0.  
>> Thanks
>> to the heads up and help from the LXD team there is a fix for this in 
>> Juju
>> master that will be available in the release next week.  However, until 
>> then
>> Juju 2.0-beta3 will not work with the latest LXD (v2.0.0-rc8).
>
>
> If you `dpkg-reconfigure lxd` and name the bridge "lxcbr0", does this
> work for beta3? I've been able to bootstrap with latest LXD and current 
> Juju
> master (beta4) by configuring LXD this way.
>
>>
>>
>> Alexis
>>
>> --
>> Alexis Bruemmer
>> Juju Core Manager, Canonical Ltd.
>> (503) 686-5018
>> alexis.bruem...@canonical.com
>>
>> --
>> Juju mailing list
>> j...@lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju
>>
>
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>


 --
 Juju-dev mailing list
 Juju-dev@lists.ubuntu.com
 Modify settings or unsubscribe at:
 https://lists.ubuntu.com/mailman/listinfo/juju-dev

>>>
>>>
>>>
>>> --
>>> Andrew McDermott 
>>> Juju Core Sapphire team 
>>>
>>> --
>>> Juju-dev mailing list
>>> Juju-dev@lists.ubuntu.com
>>> Modify settings or unsubscribe at:
>>>

Re: LXD v2.0.0-rc8 does not work with Juju v2.0-beta3

2016-04-06 Thread Pete Vander Giessen 
Hi All,

Thank you very much for posting this thread. I've been following the
"getting started" developer's guide at
https://jujucharms.com/docs/devel/getting-started, and this info got me
unstuck.

I figured that I'd mention that, when I ran dpkg-reconfigure, I had to
create an ipv4 subnet, rather than letting lxd use a proxy, as it does by
default on a fresh install of Xenial. I'm not sure if it's necessarily
related to the bridge issue, but I figured I'd be chatty about it in this
thread, just in case it helps someone else get themselves unblocked, too
(relevant debug logs posted below my sig).

Thanks again,

~ PeteVG

Logs from my install, before explicitly setting up the subnet:

~$ juju bootstrap --config default-series=xenial lxd-test lxd --debug
2016-04-07 03:51:01 INFO juju.cmd supercommand.go:60 running juju
[2.0-beta3 gc go1.6]
2016-04-07 03:51:01 INFO cmd cmd.go:141 cloud "lxd" not found, trying as a
provider name
2016-04-07 03:51:01 INFO cmd cmd.go:141 no credentials found, checking
environment
2016-04-07 03:51:01 DEBUG juju.cmd.juju.commands bootstrap.go:363 preparing
controller with config: map[default-series:xenial type:lxd name:admin
uuid:9925cf81-618b-4d50-8f77-b16447c921d8
controller-uuid:9925cf81-618b-4d50-8f77-b16447c921d8]
2016-04-07 03:51:01 ERROR cmd supercommand.go:448 invalid config: no
addresses match


On Wed, Apr 6, 2016 at 5:30 PM Reed O'Brien 
wrote:

> The rename works if you haven't removed `lxc1` which removes the original
> `lxcbr0`. If you have you will need to correctly configure another bridge
> as the new `lxcbr0` that is created has the same configuration as `lxdbr0`
> if you configured an `lxdbr0`... For me this led to two bridges with the
> same address info, which didn't work out so slick.
>
> Also, you need to `systemctl stop lxd-bridge.service && systemctl restart
> lxd.service` in the correct order.
>
> On Wed, Apr 6, 2016 at 2:22 PM, Andrew McDermott <
> andrew.mcderm...@canonical.com> wrote:
>
>> I think you'll need to `service lxd-bridge restart' in either case.
>>
>> On 6 April 2016 at 22:18, Horacio Duran 
>> wrote:
>>
>>> yes, that workaround works, also you can change /etc/default/lxd-bridge
>>> and restart the lxd-bridge service.
>>>
>>> On Wed, Apr 6, 2016 at 6:12 PM, Casey Marshall <
>>> casey.marsh...@canonical.com> wrote:
>>>
 On Wed, Apr 6, 2016 at 2:51 PM, Alexis Bruemmer <
 alexis.bruem...@canonical.com> wrote:

>
> Hi All,
>
> As recently highlighted in bug https://bugs.launchpad.net/bugs/1566589 the
> latest LXD will not work with Juju 2.0-beta3.  This is a result of LXD
> moving to use a default bridge of lxdbr0 and Juju expecting lxcbr0.  
> Thanks
> to the heads up and help from the LXD team there is a fix for this in Juju
> master that will be available in the release next week.  However, until
> then Juju 2.0-beta3 will not work with the latest LXD (v2.0.0-rc8).
>

 If you `dpkg-reconfigure lxd` and name the bridge "lxcbr0", does this
 work for beta3? I've been able to bootstrap with latest LXD and current
 Juju master (beta4) by configuring LXD this way.


>
> Alexis
>
> --
> Alexis Bruemmer
> Juju Core Manager, Canonical Ltd.
> (503) 686-5018
> alexis.bruem...@canonical.com
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
>

 --
 Juju-dev mailing list
 juju-...@lists.ubuntu.com
 Modify settings or unsubscribe at:
 https://lists.ubuntu.com/mailman/listinfo/juju-dev


>>>
>>> --
>>> Juju-dev mailing list
>>> juju-...@lists.ubuntu.com
>>> Modify settings or unsubscribe at:
>>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>>>
>>>
>>
>>
>> --
>> Andrew McDermott 
>> Juju Core Sapphire team 
>>
>> --
>> Juju-dev mailing list
>> juju-...@lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>>
>>
>
>
> --
> Reed O'Brien
> ✉ reed.obr...@canonical.com
> ✆ 415-562-6797
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: LXD v2.0.0-rc8 does not work with Juju v2.0-beta3

2016-04-06 Thread Reed O'Brien 
The rename works if you haven't removed `lxc1` which removes the original
`lxcbr0`. If you have you will need to correctly configure another bridge
as the new `lxcbr0` that is created has the same configuration as `lxdbr0`
if you configured an `lxdbr0`... For me this led to two bridges with the
same address info, which didn't work out so slick.

Also, you need to `systemctl stop lxd-bridge.service && systemctl restart
lxd.service` in the correct order.

On Wed, Apr 6, 2016 at 2:22 PM, Andrew McDermott <
andrew.mcderm...@canonical.com> wrote:

> I think you'll need to `service lxd-bridge restart' in either case.
>
> On 6 April 2016 at 22:18, Horacio Duran 
> wrote:
>
>> yes, that workaround works, also you can change /etc/default/lxd-bridge
>> and restart the lxd-bridge service.
>>
>> On Wed, Apr 6, 2016 at 6:12 PM, Casey Marshall <
>> casey.marsh...@canonical.com> wrote:
>>
>>> On Wed, Apr 6, 2016 at 2:51 PM, Alexis Bruemmer <
>>> alexis.bruem...@canonical.com> wrote:
>>>

 Hi All,

 As recently highlighted in bug https://bugs.launchpad.net/bugs/1566589 the
 latest LXD will not work with Juju 2.0-beta3.  This is a result of LXD
 moving to use a default bridge of lxdbr0 and Juju expecting lxcbr0.  Thanks
 to the heads up and help from the LXD team there is a fix for this in Juju
 master that will be available in the release next week.  However, until
 then Juju 2.0-beta3 will not work with the latest LXD (v2.0.0-rc8).

>>>
>>> If you `dpkg-reconfigure lxd` and name the bridge "lxcbr0", does this
>>> work for beta3? I've been able to bootstrap with latest LXD and current
>>> Juju master (beta4) by configuring LXD this way.
>>>
>>>

 Alexis

 --
 Alexis Bruemmer
 Juju Core Manager, Canonical Ltd.
 (503) 686-5018
 alexis.bruem...@canonical.com

 --
 Juju mailing list
 Juju@lists.ubuntu.com
 Modify settings or unsubscribe at:
 https://lists.ubuntu.com/mailman/listinfo/juju


>>>
>>> --
>>> Juju-dev mailing list
>>> juju-...@lists.ubuntu.com
>>> Modify settings or unsubscribe at:
>>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>>>
>>>
>>
>> --
>> Juju-dev mailing list
>> juju-...@lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>>
>>
>
>
> --
> Andrew McDermott 
> Juju Core Sapphire team 
>
> --
> Juju-dev mailing list
> juju-...@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
>


-- 
Reed O'Brien
✉ reed.obr...@canonical.com
✆ 415-562-6797
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: LXD v2.0.0-rc8 does not work with Juju v2.0-beta3

2016-04-06 Thread Reed O'Brien 
The rename works if you haven't removed `lxc1` which removes the original
`lxcbr0`. If you have you will need to correctly configure another bridge
as the new `lxcbr0` that is created has the same configuration as `lxdbr0`
if you configured an `lxdbr0`... For me this led to two bridges with the
same address info, which didn't work out so slick.

Also, you need to `systemctl stop lxd-bridge.service && systemctl restart
lxd.service` in the correct order.

On Wed, Apr 6, 2016 at 2:22 PM, Andrew McDermott <
andrew.mcderm...@canonical.com> wrote:

> I think you'll need to `service lxd-bridge restart' in either case.
>
> On 6 April 2016 at 22:18, Horacio Duran 
> wrote:
>
>> yes, that workaround works, also you can change /etc/default/lxd-bridge
>> and restart the lxd-bridge service.
>>
>> On Wed, Apr 6, 2016 at 6:12 PM, Casey Marshall <
>> casey.marsh...@canonical.com> wrote:
>>
>>> On Wed, Apr 6, 2016 at 2:51 PM, Alexis Bruemmer <
>>> alexis.bruem...@canonical.com> wrote:
>>>

 Hi All,

 As recently highlighted in bug https://bugs.launchpad.net/bugs/1566589 the
 latest LXD will not work with Juju 2.0-beta3.  This is a result of LXD
 moving to use a default bridge of lxdbr0 and Juju expecting lxcbr0.  Thanks
 to the heads up and help from the LXD team there is a fix for this in Juju
 master that will be available in the release next week.  However, until
 then Juju 2.0-beta3 will not work with the latest LXD (v2.0.0-rc8).

>>>
>>> If you `dpkg-reconfigure lxd` and name the bridge "lxcbr0", does this
>>> work for beta3? I've been able to bootstrap with latest LXD and current
>>> Juju master (beta4) by configuring LXD this way.
>>>
>>>

 Alexis

 --
 Alexis Bruemmer
 Juju Core Manager, Canonical Ltd.
 (503) 686-5018
 alexis.bruem...@canonical.com

 --
 Juju mailing list
 j...@lists.ubuntu.com
 Modify settings or unsubscribe at:
 https://lists.ubuntu.com/mailman/listinfo/juju


>>>
>>> --
>>> Juju-dev mailing list
>>> Juju-dev@lists.ubuntu.com
>>> Modify settings or unsubscribe at:
>>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>>>
>>>
>>
>> --
>> Juju-dev mailing list
>> Juju-dev@lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>>
>>
>
>
> --
> Andrew McDermott 
> Juju Core Sapphire team 
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
>


-- 
Reed O'Brien
✉ reed.obr...@canonical.com
✆ 415-562-6797
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: LXD v2.0.0-rc8 does not work with Juju v2.0-beta3

2016-04-06 Thread Andrew McDermott 
I think you'll need to `service lxd-bridge restart' in either case.

On 6 April 2016 at 22:18, Horacio Duran  wrote:

> yes, that workaround works, also you can change /etc/default/lxd-bridge
> and restart the lxd-bridge service.
>
> On Wed, Apr 6, 2016 at 6:12 PM, Casey Marshall <
> casey.marsh...@canonical.com> wrote:
>
>> On Wed, Apr 6, 2016 at 2:51 PM, Alexis Bruemmer <
>> alexis.bruem...@canonical.com> wrote:
>>
>>>
>>> Hi All,
>>>
>>> As recently highlighted in bug https://bugs.launchpad.net/bugs/1566589 the
>>> latest LXD will not work with Juju 2.0-beta3.  This is a result of LXD
>>> moving to use a default bridge of lxdbr0 and Juju expecting lxcbr0.  Thanks
>>> to the heads up and help from the LXD team there is a fix for this in Juju
>>> master that will be available in the release next week.  However, until
>>> then Juju 2.0-beta3 will not work with the latest LXD (v2.0.0-rc8).
>>>
>>
>> If you `dpkg-reconfigure lxd` and name the bridge "lxcbr0", does this
>> work for beta3? I've been able to bootstrap with latest LXD and current
>> Juju master (beta4) by configuring LXD this way.
>>
>>
>>>
>>> Alexis
>>>
>>> --
>>> Alexis Bruemmer
>>> Juju Core Manager, Canonical Ltd.
>>> (503) 686-5018
>>> alexis.bruem...@canonical.com
>>>
>>> --
>>> Juju mailing list
>>> Juju@lists.ubuntu.com
>>> Modify settings or unsubscribe at:
>>> https://lists.ubuntu.com/mailman/listinfo/juju
>>>
>>>
>>
>> --
>> Juju-dev mailing list
>> juju-...@lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>>
>>
>
> --
> Juju-dev mailing list
> juju-...@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
>


-- 
Andrew McDermott 
Juju Core Sapphire team 
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: LXD v2.0.0-rc8 does not work with Juju v2.0-beta3

2016-04-06 Thread Andrew McDermott 
I think you'll need to `service lxd-bridge restart' in either case.

On 6 April 2016 at 22:18, Horacio Duran  wrote:

> yes, that workaround works, also you can change /etc/default/lxd-bridge
> and restart the lxd-bridge service.
>
> On Wed, Apr 6, 2016 at 6:12 PM, Casey Marshall <
> casey.marsh...@canonical.com> wrote:
>
>> On Wed, Apr 6, 2016 at 2:51 PM, Alexis Bruemmer <
>> alexis.bruem...@canonical.com> wrote:
>>
>>>
>>> Hi All,
>>>
>>> As recently highlighted in bug https://bugs.launchpad.net/bugs/1566589 the
>>> latest LXD will not work with Juju 2.0-beta3.  This is a result of LXD
>>> moving to use a default bridge of lxdbr0 and Juju expecting lxcbr0.  Thanks
>>> to the heads up and help from the LXD team there is a fix for this in Juju
>>> master that will be available in the release next week.  However, until
>>> then Juju 2.0-beta3 will not work with the latest LXD (v2.0.0-rc8).
>>>
>>
>> If you `dpkg-reconfigure lxd` and name the bridge "lxcbr0", does this
>> work for beta3? I've been able to bootstrap with latest LXD and current
>> Juju master (beta4) by configuring LXD this way.
>>
>>
>>>
>>> Alexis
>>>
>>> --
>>> Alexis Bruemmer
>>> Juju Core Manager, Canonical Ltd.
>>> (503) 686-5018
>>> alexis.bruem...@canonical.com
>>>
>>> --
>>> Juju mailing list
>>> j...@lists.ubuntu.com
>>> Modify settings or unsubscribe at:
>>> https://lists.ubuntu.com/mailman/listinfo/juju
>>>
>>>
>>
>> --
>> Juju-dev mailing list
>> Juju-dev@lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>>
>>
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
>


-- 
Andrew McDermott 
Juju Core Sapphire team 
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: LXD v2.0.0-rc8 does not work with Juju v2.0-beta3

2016-04-06 Thread Horacio Duran 
yes, that workaround works, also you can change /etc/default/lxd-bridge and
restart the lxd-bridge service.

On Wed, Apr 6, 2016 at 6:12 PM, Casey Marshall  wrote:

> On Wed, Apr 6, 2016 at 2:51 PM, Alexis Bruemmer <
> alexis.bruem...@canonical.com> wrote:
>
>>
>> Hi All,
>>
>> As recently highlighted in bug https://bugs.launchpad.net/bugs/1566589 the
>> latest LXD will not work with Juju 2.0-beta3.  This is a result of LXD
>> moving to use a default bridge of lxdbr0 and Juju expecting lxcbr0.  Thanks
>> to the heads up and help from the LXD team there is a fix for this in Juju
>> master that will be available in the release next week.  However, until
>> then Juju 2.0-beta3 will not work with the latest LXD (v2.0.0-rc8).
>>
>
> If you `dpkg-reconfigure lxd` and name the bridge "lxcbr0", does this work
> for beta3? I've been able to bootstrap with latest LXD and current Juju
> master (beta4) by configuring LXD this way.
>
>
>>
>> Alexis
>>
>> --
>> Alexis Bruemmer
>> Juju Core Manager, Canonical Ltd.
>> (503) 686-5018
>> alexis.bruem...@canonical.com
>>
>> --
>> Juju mailing list
>> Juju@lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju
>>
>>
>
> --
> Juju-dev mailing list
> juju-...@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: LXD v2.0.0-rc8 does not work with Juju v2.0-beta3

2016-04-06 Thread Horacio Duran 
yes, that workaround works, also you can change /etc/default/lxd-bridge and
restart the lxd-bridge service.

On Wed, Apr 6, 2016 at 6:12 PM, Casey Marshall  wrote:

> On Wed, Apr 6, 2016 at 2:51 PM, Alexis Bruemmer <
> alexis.bruem...@canonical.com> wrote:
>
>>
>> Hi All,
>>
>> As recently highlighted in bug https://bugs.launchpad.net/bugs/1566589 the
>> latest LXD will not work with Juju 2.0-beta3.  This is a result of LXD
>> moving to use a default bridge of lxdbr0 and Juju expecting lxcbr0.  Thanks
>> to the heads up and help from the LXD team there is a fix for this in Juju
>> master that will be available in the release next week.  However, until
>> then Juju 2.0-beta3 will not work with the latest LXD (v2.0.0-rc8).
>>
>
> If you `dpkg-reconfigure lxd` and name the bridge "lxcbr0", does this work
> for beta3? I've been able to bootstrap with latest LXD and current Juju
> master (beta4) by configuring LXD this way.
>
>
>>
>> Alexis
>>
>> --
>> Alexis Bruemmer
>> Juju Core Manager, Canonical Ltd.
>> (503) 686-5018
>> alexis.bruem...@canonical.com
>>
>> --
>> Juju mailing list
>> j...@lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju
>>
>>
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
>
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: LXD v2.0.0-rc8 does not work with Juju v2.0-beta3

2016-04-06 Thread Casey Marshall 
On Wed, Apr 6, 2016 at 2:51 PM, Alexis Bruemmer <
alexis.bruem...@canonical.com> wrote:

>
> Hi All,
>
> As recently highlighted in bug https://bugs.launchpad.net/bugs/1566589 the
> latest LXD will not work with Juju 2.0-beta3.  This is a result of LXD
> moving to use a default bridge of lxdbr0 and Juju expecting lxcbr0.  Thanks
> to the heads up and help from the LXD team there is a fix for this in Juju
> master that will be available in the release next week.  However, until
> then Juju 2.0-beta3 will not work with the latest LXD (v2.0.0-rc8).
>

If you `dpkg-reconfigure lxd` and name the bridge "lxcbr0", does this work
for beta3? I've been able to bootstrap with latest LXD and current Juju
master (beta4) by configuring LXD this way.


>
> Alexis
>
> --
> Alexis Bruemmer
> Juju Core Manager, Canonical Ltd.
> (503) 686-5018
> alexis.bruem...@canonical.com
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: LXD v2.0.0-rc8 does not work with Juju v2.0-beta3

2016-04-06 Thread Casey Marshall 
On Wed, Apr 6, 2016 at 2:51 PM, Alexis Bruemmer <
alexis.bruem...@canonical.com> wrote:

>
> Hi All,
>
> As recently highlighted in bug https://bugs.launchpad.net/bugs/1566589 the
> latest LXD will not work with Juju 2.0-beta3.  This is a result of LXD
> moving to use a default bridge of lxdbr0 and Juju expecting lxcbr0.  Thanks
> to the heads up and help from the LXD team there is a fix for this in Juju
> master that will be available in the release next week.  However, until
> then Juju 2.0-beta3 will not work with the latest LXD (v2.0.0-rc8).
>

If you `dpkg-reconfigure lxd` and name the bridge "lxcbr0", does this work
for beta3? I've been able to bootstrap with latest LXD and current Juju
master (beta4) by configuring LXD this way.


>
> Alexis
>
> --
> Alexis Bruemmer
> Juju Core Manager, Canonical Ltd.
> (503) 686-5018
> alexis.bruem...@canonical.com
>
> --
> Juju mailing list
> j...@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
>
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev