Re: [lxc-users] containers and lxdbr0 bridge lost ip after upgrade on 2.18

2017-09-27 Thread Laurent Ducos
Yes it's a dnsmasq version parsing issue
Thanks for the fix
26 septembre 2017 15:07 "Stéphane Graber"  a écrit:
> On Fri, Sep 22, 2017 at 02:29:15PM +, Laurent Ducos wrote:
> 
>> Hello 
>> After xenial ubuntu upgrade lxd switch to  2.18
>> i reboot and no ip for lxdbr0 and no ip for container
>> It set manualy ip for lxdbr0 "sudo ip addr add dev lxdbr0 10.215.181.1/24" 
>> and launch a container
>> but  always no ip 
>> Here is syslog entry when i try to start the container
>> 
>> Sep 22 16:18:07 blabla kernel: [ 3482.496088] lxdbr0: port 1(vethFVYDNI) 
>> entered disabled state
>> Sep 22 16:18:07 blabla kernel: [ 3482.501486] device vethFVYDNI left 
>> promiscuous mode
>> Sep 22 16:18:07 blabla kernel: [ 3482.501490] lxdbr0: port 1(vethFVYDNI) 
>> entered disabled state
>> Sep 22 16:18:08 blabla kernel: [ 3483.329216] audit: type=1400 
>> audit(1506089888.350:166):
>> apparmor="STATUS" operation="profile_remove" profile="unconfined" 
>> name="lxd-user10-blabla-sandbox_"
>> pid=77593 comm="apparmor_parser"
>> Sep 22 16:18:16 blabla kernel: [ 3491.046769] audit: type=1400 
>> audit(1506089896.070:167):
>> apparmor="STATUS" operation="profile_load" profile="unconfined" 
>> name="lxd-user10-blabla-sandbox_"
>> pid=77629 comm="apparmor_parser"
>> Sep 22 16:18:16 blabla systemd-udevd[77631]: Could not generate persistent 
>> MAC address for
>> vethB22DLS: No such file or directory
>> Sep 22 16:18:16 blabla kernel: [ 3491.057615] device vethCORADG entered 
>> promiscuous mode
>> Sep 22 16:18:16 blabla kernel: [ 3491.057808] IPv6: ADDRCONF(NETDEV_UP): 
>> vethCORADG: link is not
>> ready
>> Sep 22 16:18:16 blabla kernel: [ 3491.146758] eth0: renamed from vethB22DLS
>> Sep 22 16:18:16 blabla kernel: [ 3491.167857] IPv6: ADDRCONF(NETDEV_CHANGE): 
>> vethCORADG: link
>> becomes ready
>> Sep 22 16:18:16 blabla kernel: [ 3491.167961] lxdbr0: port 1(vethCORADG) 
>> entered forwarding state
>> Sep 22 16:18:16 blabla kernel: [ 3491.167971] lxdbr0: port 1(vethCORADG) 
>> entered forwarding state
>> Sep 22 16:18:31 blabla kernel: [ 3506.214893] lxdbr0: port 1(vethCORADG) 
>> entered forwarding state
>> my network configuration
>> config:
>> dns.domain: blabla.local
>> dns.mode: dynamic
>> ipv4.address: 10.215.181.1/24
>> ipv4.nat: "true"
>> description: ""
>> name: lxdbr0
>> type: bridge
>> used_by:
>> - /1.0/containers/lxd-user10-blabla-sandbox
> 
> Hi,
> 
> That sounds like the dnsmasq version parsing issue we fixed a few days ago.
> 
> Can you paste "dnsmasq --version" so we can make sure the new code
> handles your output properly?
> 
> --
> Stéphane Graber
> Ubuntu developer
> http://www.ubuntu.com
> 
> ___
> lxc-users mailing list
> lxc-users@lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] containers and lxdbr0 bridge lost ip after upgrade on 2.18

2017-09-26 Thread Stéphane Graber
On Fri, Sep 22, 2017 at 02:29:15PM +, Laurent Ducos wrote:
> Hello 
> After xenial ubuntu upgrade lxd switch to  2.18
> i reboot and no ip for lxdbr0 and no ip for container
> It set manualy ip for lxdbr0 "sudo ip addr add dev lxdbr0 10.215.181.1/24" 
> and launch a container but  always no ip 
> Here is syslog entry when i try to start the container
> 
> Sep 22 16:18:07 blabla kernel: [ 3482.496088] lxdbr0: port 1(vethFVYDNI) 
> entered disabled state
> Sep 22 16:18:07 blabla kernel: [ 3482.501486] device vethFVYDNI left 
> promiscuous mode
> Sep 22 16:18:07 blabla kernel: [ 3482.501490] lxdbr0: port 1(vethFVYDNI) 
> entered disabled state
> Sep 22 16:18:08 blabla kernel: [ 3483.329216] audit: type=1400 
> audit(1506089888.350:166): apparmor="STATUS" operation="profile_remove" 
> profile="unconfined" name="lxd-user10-blabla-sandbox_" pid=77593 
> comm="apparmor_parser"
> Sep 22 16:18:16 blabla kernel: [ 3491.046769] audit: type=1400 
> audit(1506089896.070:167): apparmor="STATUS" operation="profile_load" 
> profile="unconfined" name="lxd-user10-blabla-sandbox_" pid=77629 
> comm="apparmor_parser"
> Sep 22 16:18:16 blabla systemd-udevd[77631]: Could not generate persistent 
> MAC address for vethB22DLS: No such file or directory
> Sep 22 16:18:16 blabla kernel: [ 3491.057615] device vethCORADG entered 
> promiscuous mode
> Sep 22 16:18:16 blabla kernel: [ 3491.057808] IPv6: ADDRCONF(NETDEV_UP): 
> vethCORADG: link is not ready
> Sep 22 16:18:16 blabla kernel: [ 3491.146758] eth0: renamed from vethB22DLS
> Sep 22 16:18:16 blabla kernel: [ 3491.167857] IPv6: ADDRCONF(NETDEV_CHANGE): 
> vethCORADG: link becomes ready
> Sep 22 16:18:16 blabla kernel: [ 3491.167961] lxdbr0: port 1(vethCORADG) 
> entered forwarding state
> Sep 22 16:18:16 blabla kernel: [ 3491.167971] lxdbr0: port 1(vethCORADG) 
> entered forwarding state
> Sep 22 16:18:31 blabla kernel: [ 3506.214893] lxdbr0: port 1(vethCORADG) 
> entered forwarding state
> my network configuration
> config:
>   dns.domain: blabla.local
>   dns.mode: dynamic
>   ipv4.address: 10.215.181.1/24
>   ipv4.nat: "true"
> description: ""
> name: lxdbr0
> type: bridge
> used_by:
> - /1.0/containers/lxd-user10-blabla-sandbox

Hi,

That sounds like the dnsmasq version parsing issue we fixed a few days ago.

Can you paste "dnsmasq --version" so we can make sure the new code
handles your output properly?

-- 
Stéphane Graber
Ubuntu developer
http://www.ubuntu.com


signature.asc
Description: PGP signature
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

[lxc-users] containers and lxdbr0 bridge lost ip after upgrade on 2.18

2017-09-22 Thread Laurent Ducos
Hello 
After xenial ubuntu upgrade lxd switch to  2.18
i reboot and no ip for lxdbr0 and no ip for container
It set manualy ip for lxdbr0 "sudo ip addr add dev lxdbr0 10.215.181.1/24" and 
launch a container but  always no ip 
Here is syslog entry when i try to start the container

Sep 22 16:18:07 blabla kernel: [ 3482.496088] lxdbr0: port 1(vethFVYDNI) 
entered disabled state
Sep 22 16:18:07 blabla kernel: [ 3482.501486] device vethFVYDNI left 
promiscuous mode
Sep 22 16:18:07 blabla kernel: [ 3482.501490] lxdbr0: port 1(vethFVYDNI) 
entered disabled state
Sep 22 16:18:08 blabla kernel: [ 3483.329216] audit: type=1400 
audit(1506089888.350:166): apparmor="STATUS" operation="profile_remove" 
profile="unconfined" name="lxd-user10-blabla-sandbox_" pid=77593 
comm="apparmor_parser"
Sep 22 16:18:16 blabla kernel: [ 3491.046769] audit: type=1400 
audit(1506089896.070:167): apparmor="STATUS" operation="profile_load" 
profile="unconfined" name="lxd-user10-blabla-sandbox_" pid=77629 
comm="apparmor_parser"
Sep 22 16:18:16 blabla systemd-udevd[77631]: Could not generate persistent MAC 
address for vethB22DLS: No such file or directory
Sep 22 16:18:16 blabla kernel: [ 3491.057615] device vethCORADG entered 
promiscuous mode
Sep 22 16:18:16 blabla kernel: [ 3491.057808] IPv6: ADDRCONF(NETDEV_UP): 
vethCORADG: link is not ready
Sep 22 16:18:16 blabla kernel: [ 3491.146758] eth0: renamed from vethB22DLS
Sep 22 16:18:16 blabla kernel: [ 3491.167857] IPv6: ADDRCONF(NETDEV_CHANGE): 
vethCORADG: link becomes ready
Sep 22 16:18:16 blabla kernel: [ 3491.167961] lxdbr0: port 1(vethCORADG) 
entered forwarding state
Sep 22 16:18:16 blabla kernel: [ 3491.167971] lxdbr0: port 1(vethCORADG) 
entered forwarding state
Sep 22 16:18:31 blabla kernel: [ 3506.214893] lxdbr0: port 1(vethCORADG) 
entered forwarding state
my network configuration
config:
  dns.domain: blabla.local
  dns.mode: dynamic
  ipv4.address: 10.215.181.1/24
  ipv4.nat: "true"
description: ""
name: lxdbr0
type: bridge
used_by:
- /1.0/containers/lxd-user10-blabla-sandbox
 
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users