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

Thu Apr 7 14:57:28 UTC 2016

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" <roger.peppe at canonical.com> 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 <petevg at gmail.com> 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.obrien at 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`
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.mcdermott at 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 <horacio.duran at canonical.com>
>>> 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.marshall at canonical.com> wrote:
>>>>>
>>>>> On Wed, Apr 6, 2016 at 2:51 PM, Alexis Bruemmer
>>>>> <alexis.bruemmer at 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.bruemmer at canonical.com
>>>>>>
>>>>>> --
>>>>>> Juju mailing list
>>>>>> Juju at lists.ubuntu.com
>>>>>> Modify settings or unsubscribe at:
>>>>>> https://lists.ubuntu.com/mailman/listinfo/juju
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Juju-dev mailing list
>>>>> Juju-dev at lists.ubuntu.com
>>>>> Modify settings or unsubscribe at:
>>>>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>>>>>
>>>>
>>>>
>>>> --
>>>> Juju-dev mailing list
>>>> Juju-dev at lists.ubuntu.com
>>>> Modify settings or unsubscribe at:
>>>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Andrew McDermott <andrew.mcdermott at canonical.com>
>>> Juju Core Sapphire team <http://juju.ubuntu.com>
>>>
>>> --
>>> Juju-dev mailing list
>>> Juju-dev at lists.ubuntu.com
>>> Modify settings or unsubscribe at:
>>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>>>
>>
>>
>>
>> --
>> Reed O'Brien
>> ✉ reed.obrien at canonical.com
>> ✆ 415-562-6797
>>
>> --
>> Juju mailing list
>> Juju at lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju
>
>
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>

--
Juju-dev mailing list
Juju-dev at lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20160407/c454f737/attachment-0001.html>