<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hey everyone,<br>
<br>
I'm seeing a strange behavior when using lxd profiles to attach the container eth devices to the host bridges.<br>
I see some inconsistency: I made two bridges on my host and want to use the profiles to associate the container eth0 to one bridge, and eth1 to the other. Somehow, the eth0 and eth1 end up being assigned to the wrong bridges (swapped).<br>
Here's the full output from lxd, showing the profiles and the bridges. At the end you'll see each of the container interfaces attached to the wrong bridge:<br>
<br>
#####<br>
<br>
me@host:~$ lxc profile show dev_br23<br>
name: dev_br23<br>
config: {}<br>
description: ""<br>
devices:<br>
eth1:<br>
nictype: bridged<br>
parent: br23<br>
type: nic<br>
me@host:~$ lxc profile show dev_br250<br>
name: dev_br250<br>
config: {}<br>
description: ""<br>
devices:<br>
eth0:<br>
nictype: bridged<br>
parent: br250<br>
type: nic<br>
<br>
<br>
me@host:~$ lxc profile apply lbng1-internal dev_br23,dev_br250<br>
Profile dev_br23,dev_br250 applied to lbng1-internal<br>
me@host:~$<br>
me@host:~$ lxc config show lbng1-internal<br>
name: lbng1-internal<br>
profiles:<br>
- dev_br23<br>
- dev_br250<br>
config:<br>
boot.autostart: "true"<br>
volatile.base_image: 5bcef3ad83936c18d45cd866f38cd2cab53bcd28fa38478166a57c404537ec1f<br>
volatile.eth0.hwaddr: 00:16:3e:75:5c:3d<br>
volatile.eth0.name: eth1<br>
volatile.eth1.hwaddr: 00:16:3e:9d:8f:c7<br>
volatile.eth1.name: eth0<br>
volatile.last_state.idmap: '[{"Isuid":true,"Isgid":false,"Hostid":231072,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":231072,"Nsid":0,"Maprange":65536}]'<br>
devices:<br>
root:<br>
path: /<br>
type: disk<br>
ephemeral: false<br>
<br>
me@host:~$ brctl show<br>
bridge name bridge id STP enabled interfaces<br>
br23 8000.5254001c2c55 no eth2<br>
vethASE3RF<br>
vethB03UPX<br>
br250 8000.525400256f8e no eth1<br>
veth5AYAW8<br>
vethAB1VM9<br>
vethH2QO2P<br>
vethUA3SUE<br>
vethYPM4BL<br>
<br>
<br>
<br>
me@host:~$ lxc info lbng1-internal<br>
Name: lbng1-internal<br>
Architecture: x86_64<br>
Created: 2016/03/31 08:23 UTC<br>
Status: Running<br>
Type: persistent<br>
Profiles: dev_br23, dev_br250<br>
Pid: 17528<br>
Processes: 27<br>
Ips:<br>
eth0: inet 10.35.15.28 vethASE3RF<br>
eth0: inet6 fe80::216:3eff:fe9d:8fc7 vethASE3RF<br>
eth1: inet6 fe80::216:3eff:fe75:5c3d vethH2QO2P<br>
lo: inet 127.0.0.1<br>
lo: inet6 ::1<br>
<br>
####<br>
<br>
Am I missing something very obvious?<br>
Thanks!<br>
<p class="MsoNormal"><span style="font-size:8.0pt;mso-ascii-font-family:Calibri, sans-serif;
mso-ascii-theme-font:minor-latin;mso-hansi-font-family:Calibri;mso-hansi-theme-font:
minor-latin"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;mso-ascii-font-family:Calibri, sans-serif;
mso-ascii-theme-font:minor-latin;mso-hansi-font-family:Calibri;mso-hansi-theme-font:
minor-latin">CONFIDENTIALITY NOTICE: This email message (and any attachment)
is intended only for the individual or entity to which it is addressed. The information in this email is confidential and may contain information that is legally privileged or exempt from disclosure under applicable law. If you are not the intended recipient,
you are strictly prohibited from reading, using, publishing or disseminating such information and upon receipt, must permanently delete the original and destroy any copies. We take steps to protect against viruses and other defects but advise you to carry
out your own checks and precautions as Kambi does not accept any liability for any which remain. Thank you for your co-operation.
<o:p></o:p></span></p>
</body>
</html>