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,
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,
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
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
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:
> 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
> 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
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:
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:
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
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
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
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
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.
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.
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
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
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,
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
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
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,
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,
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
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
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
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
26 matches
Mail list logo