Hello
I’m trying to use 8021Q Network Driver with LXC. Network driver operation pre failed. I managed to bypass that but now post operation also failed. These are the logs:
Wed Jan 20 15:24:11 2016 [Z0][VM][I]: New state is ACTIVE
Wed Jan 20 15:24:12 2016 [Z0][VM][I]: New LCM state is PROLOG
Wed Jan 20 15:24:13 2016 [Z0][VM][I]: New LCM state is BOOT
Wed Jan 20 15:24:13 2016 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/70/deployment.0
Wed Jan 20 15:24:14 2016 [Z0][VMM][I]: pre: Executed “sudo brctl addbr onebr”.
Wed Jan 20 15:24:14 2016 [Z0][VMM][I]: pre: Executed “sudo ip link set onebr up”.
Wed Jan 20 15:24:14 2016 [Z0][VMM][I]: pre: Executed “sudo ip link add link eth0 name eth0.987 type vlan id 987”.
Wed Jan 20 15:24:14 2016 [Z0][VMM][I]: pre: Executed “sudo ip link set eth0.987 up”.
Wed Jan 20 15:24:14 2016 [Z0][VMM][I]: pre: Executed “sudo brctl addif onebr eth0.987”.
Wed Jan 20 15:24:14 2016 [Z0][VMM][I]: ExitCode: 0
Wed Jan 20 15:24:14 2016 [Z0][VMM][I]: Successfully execute network driver operation: pre.
Wed Jan 20 15:24:15 2016 [Z0][VMM][I]: ExitCode: 0
Wed Jan 20 15:24:15 2016 [Z0][VMM][I]: Successfully execute virtualization driver operation: deploy.
Wed Jan 20 15:24:16 2016 [Z0][VMM][I]: Command execution fail: /var/tmp/one/vnm/802.1Q/post PFZNPjxJRD43MDwvSUQ+PERFUExPWV9JRC8+PFRFTVBMQVRFPjxOSUM+PEFSX0lEPjwhW0NEQVRBWzBdXT48L0FSX0lEPjxCUklER0U+PCFbQ0RBVEFbb25lYnJdXT48L0JSSURHRT48SVA+PCFbQ0RBVEFbMTAuOC45MS4xOTBdXT48L0lQPjxNQUM+PCFbQ0RBVEFbMDI6MDA6MGE6MDg6NWI6YmVdXT48L01BQz48TkVUV09SSz48IVtDREFUQVt2bGFuLXRlc3RdXT48L05FVFdPUks+PE5FVFdPUktfSUQ+PCFbQ0RBVEFbODJdXT48L05FVFdPUktfSUQ+PE5FVFdPUktfVU5BTUU+PCFbQ0RBVEFbb25lYWRtaW5dXT48L05FVFdPUktfVU5BTUU+PE5JQ19JRD48IVtDREFUQVswXV0+PC9OSUNfSUQ+PFBIWURFVj48IVtDREFUQVtldGgwXV0+PC9QSFlERVY+PFNFQ1VSSVRZX0dST1VQUz48IVtDREFUQVswXV0+PC9TRUNVUklUWV9HUk9VUFM+PFZMQU4+PCFbQ0RBVEFbWUVTXV0+PC9WTEFOPjxWTEFOX0lEPjwhW0NEQVRBWzk4N11dPjwvVkxBTl9JRD48L05JQz48L1RFTVBMQVRFPjxURU1QTEFURT48U0VDVVJJVFlfR1JPVVBfUlVMRT48UFJPVE9DT0w+PCFbQ0RBVEFbQUxMXV0+PC9QUk9UT0NPTD48UlVMRV9UWVBFPjwhW0NEQVRBW09VVEJPVU5EXV0+PC9SVUxFX1RZUEU+PFNFQ1VSSVRZX0dST1VQX0lEPjwhW0NEQVRBWzBdXT48L1NFQ1VSSVRZX0dST1VQX0lEPjxTRUNVUklUWV9HUk9VUF9OQU1FPjwhW0NEQVRBW2RlZmF1bHRdXT48L1NFQ1VSSVRZX0dST1VQX05BTUU+PC9TRUNVUklUWV9HUk9VUF9SVUxFPjwvVEVNUExBVEU+PFRFTVBMQVRFPjxTRUNVUklUWV9HUk9VUF9SVUxFPjxQUk9UT0NPTD48IVtDREFUQVtBTExdXT48L1BST1RPQ09MPjxSVUxFX1RZUEU+PCFbQ0RBVEFbSU5CT1VORF1dPjwvUlVMRV9UWVBFPjxTRUNVUklUWV9HUk9VUF9JRD48IVtDREFUQVswXV0+PC9TRUNVUklUWV9HUk9VUF9JRD48U0VDVVJJVFlfR1JPVVBfTkFNRT48IVtDREFUQVtkZWZhdWx0XV0+PC9TRUNVUklUWV9HUk9VUF9OQU1FPjwvU0VDVVJJVFlfR1JPVVBfUlVMRT48L1RFTVBMQVRFPjxISVNUT1JZX1JFQ09SRFM+PEhJU1RPUlk+PEhPU1ROQU1FPjEwLjguOTEuODE8L0hPU1ROQU1FPjwvSElTVE9SWT48L0hJU1RPUllfUkVDT1JEUz48L1ZNPg== ‘/dev/loop0
Wed Jan 20 15:24:16 2016 [Z0][VMM][I]: one-70’
Wed Jan 20 15:24:16 2016 [Z0][VMM][I]: iptables v1.4.21: interface name --physdev-is-bridged' must be shorter than IFNAMSIZ (15) Wed Jan 20 15:24:16 2016 [Z0][VMM][I]: Tryiptables -h’ or ‘iptables --help’ for more information.
Wed Jan 20 15:24:16 2016 [Z0][VMM][E]: post: Command Error: sudo iptables -I opennebula -m physdev --physdev-out --physdev-is-bridged -j one-70-0-i
Wed Jan 20 15:24:16 2016 [Z0][VMM][E]: post: ["/var/tmp/one/vnm/command.rb:76:in block in run!'", "/var/tmp/one/vnm/command.rb:73:ineach’", “/var/tmp/one/vnm/command.rb:73:in run!'", "/var/tmp/one/vnm/security_groups_iptables.rb:281:innic_pre’”, “/var/tmp/one/vnm/sg_driver.rb:67:in block in activate'", "/var/tmp/one/vnm/sg_driver.rb:63:ineach’”, “/var/tmp/one/vnm/sg_driver.rb:63:in activate'", "/var/tmp/one/vnm/802.1Q/post:29:in'”]
Wed Jan 20 15:24:16 2016 [Z0][VMM][I]: ExitCode: 1
Wed Jan 20 15:24:18 2016 [Z0][VMM][I]: ExitCode: 0
Wed Jan 20 15:24:18 2016 [Z0][VMM][I]: Successfully execute virtualization driver operation: cancel.
Wed Jan 20 15:24:18 2016 [Z0][VMM][I]: Failed to execute network driver operation: post.
Wed Jan 20 15:24:18 2016 [Z0][VMM][E]: Error deploying virtual machine
Wed Jan 20 15:24:18 2016 [Z0][VM][I]: New LCM state is BOOT_FAILURE
This issue is similar to this one, but the reasons aren’t the same and that fix is already implemented.
Inside /var/tmp/one/vnm/security_groups_iptables.rb I can see the line that fails:
commands.add :iptables, "-I #{GLOBAL_CHAIN} -m physdev --physdev-out #{nic[:tap]} --physdev-is-bridged -j #{chain_in}"
and comparing it with the logs output, it seems that #{nic[:tap]} has no value, but I have no idea why. I had to make a small modification inside /var/lib/one/remotes/vnm/vnm_driver.rb as explained here, don’t know if that has something to do.
Thanks