Bug #4804

802.1q Virtual Netwrok Driver Deactivate problem

Added by Kristian Feldsam about 4 years ago. Updated about 4 years ago.

Status:ClosedStart date:09/20/2016
Priority:NormalDue date:
Assignee:Jaime Melis% Done:

0%

Category:Drivers - Network
Target version:Release 5.2
Resolution: Pull request:
Affected Versions:OpenNebula 5.0

Description

Problem:

- Deploy some VMs on ex. node1 with virtual network using 802.1q driver
- Driver creates phys dev for ex. team0.205 and assign it to bridge onebr5
- Throught API call Hard Terminate all VMs that using that network on that node. So VMs are deleted in same time.
- Driver want deactivate network on that node by deleting onebr5 bridge and team0.205 interface
- Driver fails to deactivate and errors logged in VM

Mon Sep 19 23:02:17 2016 [Z0][VM][I]: New LCM state is SHUTDOWN
Mon Sep 19 23:02:18 2016 [Z0][VMM][I]: ExitCode: 0
Mon Sep 19 23:02:18 2016 [Z0][VMM][I]: Successfully execute virtualization driver operation: cancel.
Mon Sep 19 23:02:18 2016 [Z0][VMM][I]: Command execution fail: /var/tmp/one/vnm/802.1Q/clean PFZNPjxJRD4xMDc4PC9JRD48REVQTE9ZX0lEPm9uZS0xMDc4PC9ERVBMT1lfSUQ+PFRFTVBMQVRFPjxTRUNVUklUWV9HUk9VUF9SVUxFPjxQUk9UT0NPTD48IVtDREFUQVtBTExdXT48L1BST1RPQ09MPjxSVUxFX1RZUEU+PCFbQ0RBVEFbT1VUQk9VTkRdXT48L1JVTEVfVFlQRT48U0VDVVJJVFlfR1JPVVBfSUQ+PCFbQ0RBVEFbMF1dPjwvU0VDVVJJVFlfR1JPVVBfSUQ+PFNFQ1VSSVRZX0dST1VQX05BTUU+PCFbQ0RBVEFbZGVmYXVsdF1dPjwvU0VDVVJJVFlfR1JPVVBfTkFNRT48L1NFQ1VSSVRZX0dST1VQX1JVTEU+PC9URU1QTEFURT48VEVNUExBVEU+PFNFQ1VSSVRZX0dST1VQX1JVTEU+PFBST1RPQ09MPjwhW0NEQVRBW0FMTF1dPjwvUFJPVE9DT0w+PFJVTEVfVFlQRT48IVtDREFUQVtJTkJPVU5EXV0+PC9SVUxFX1RZUEU+PFNFQ1VSSVRZX0dST1VQX0lEPjwhW0NEQVRBWzBdXT48L1NFQ1VSSVRZX0dST1VQX0lEPjxTRUNVUklUWV9HUk9VUF9OQU1FPjwhW0NEQVRBW2RlZmF1bHRdXT48L1NFQ1VSSVRZX0dST1VQX05BTUU+PC9TRUNVUklUWV9HUk9VUF9SVUxFPjwvVEVNUExBVEU+PEhJU1RPUllfUkVDT1JEUz48SElTVE9SWT48SE9TVE5BTUU+bm9kZTMuZmVsZGhvc3QuY3o8L0hPU1ROQU1FPjwvSElTVE9SWT48L0hJU1RPUllfUkVDT1JEUz48SElTVE9SWV9SRUNPUkRTPjxISVNUT1JZPjxWTV9NQUQ+PCFbQ0RBVEFba3ZtXV0+PC9WTV9NQUQ+PC9ISVNUT1JZPjwvSElTVE9SWV9SRUNPUkRTPjxURU1QTEFURT48TklDPjxBUl9JRD48IVtDREFUQVswXV0+PC9BUl9JRD48QlJJREdFPjwhW0NEQVRBW29uZWJyNl1dPjwvQlJJREdFPjxDTFVTVEVSX0lEPjwhW0NEQVRBWzEwMF1dPjwvQ0xVU1RFUl9JRD48SVA+PCFbQ0RBVEFbMTAuNDYuMC4xNzddXT48L0lQPjxNQUM+PCFbQ0RBVEFbMDI6MDA6MGE6MmU6MDA6YjFdXT48L01BQz48TU9ERUw+PCFbQ0RBVEFbdmlydGlvXV0+PC9NT0RFTD48TkVUV09SSz48IVtDREFUQVtGZWVkb0RldmVsb3BdXT48L05FVFdPUks+PE5FVFdPUktfSUQ+PCFbQ0RBVEFbNl1dPjwvTkVUV09SS19JRD48TkVUV09SS19VTkFNRT48IVtDREFUQVtmZWxkc2FtXV0+PC9ORVRXT1JLX1VOQU1FPjxOSUNfSUQ+PCFbQ0RBVEFbMF1dPjwvTklDX0lEPjxQSFlERVY+PCFbQ0RBVEFbdGVhbTBdXT48L1BIWURFVj48U0VDVVJJVFlfR1JPVVBTPjwhW0NEQVRBWzBdXT48L1NFQ1VSSVRZX0dST1VQUz48VEFSR0VUPjwhW0NEQVRBW29uZS0xMDc4LTBdXT48L1RBUkdFVD48VkxBTl9JRD48IVtDREFUQVsyMDZdXT48L1ZMQU5fSUQ+PFZOX01BRD48IVtDREFUQVs4MDIuMVFdXT48L1ZOX01BRD48L05JQz48L1RFTVBMQVRFPjwvVk0+
Mon Sep 19 23:02:18 2016 [Z0][VMM][E]: clean: undefined method `length' for nil:NilClass
Mon Sep 19 23:02:18 2016 [Z0][VMM][E]: clean: ["/var/tmp/one/vnm/vlan.rb:94:in `block in deactivate'", "/var/tmp/one/vnm/vm.rb:61:in `call'", "/var/tmp/one/vnm/vm.rb:61:in `block in each_nic'", "/var/tmp/one/vnm/vm.rb:60:in `each'", "/var/tmp/one/vnm/vm.rb:60:in `each_nic'", "/var/tmp/one/vnm/vnm_driver.rb:71:in `process'", "/var/tmp/one/vnm/vlan.rb:83:in `deactivate'", "/var/tmp/one/vnm/802.1Q/clean:30:in `
'"]
Mon Sep 19 23:02:18 2016 [Z0][VMM][I]: ExitCode: 1
Mon Sep 19 23:02:18 2016 [Z0][VMM][I]: Failed to execute network driver operation: clean.
Mon Sep 19 23:02:18 2016 [Z0][VMM][E]: Error canceling VM: 802.1Q: -
Mon Sep 19 23:02:18 2016 [Z0][VM][I]: New LCM state is RUNNING
Mon Sep 19 23:02:18 2016 [Z0][LCM][I]: Fail to shutdown VM. Assuming that the VM is still RUNNING (will poll VM).
Mon Sep 19 23:04:40 2016 [Z0][LCM][I]: VM running but monitor state is POWEROFF
Mon Sep 19 23:04:40 2016 [Z0][VM][I]: New LCM state is SHUTDOWN_POWEROFF
Mon Sep 19 23:04:40 2016 [Z0][VM][I]: New state is POWEROFF
Mon Sep 19 23:04:40 2016 [Z0][VM][I]: New LCM state is LCM_INIT

This log is on all vm expect one, which was deleted successfully. Looks like, that all vm shutdown actions want to deactivate network, but only want can exit with 0.

Associated revisions

Revision e1e6a8bf
Added by Jaime Melis about 4 years ago

B #4804: 802.1Q Virtual Network Driver Deactivate problem

Revision b0954bf6
Added by Jaime Melis about 4 years ago

B #4804: Fixes invalid patch

History

#1 Updated by Ruben S. Montero about 4 years ago

  • Category set to Drivers - Network
  • Assignee set to Jaime Melis

#2 Updated by Jaime Melis about 4 years ago

  • Status changed from Pending to Closed
  • Resolution set to fixed

#3 Updated by Kristian Feldsam about 4 years ago

Hello, I try your patch, but I got this error when deploying machine

Fri Sep 23 16:47:24 2016 [Z0][VMM][I]: Command execution fail: /var/tmp/one/vnm/802.1Q/pre PFZNPjxJRD4xMzIxPC9JRD48REVQTE9ZX0lELz48VEVNUExBVEU+PFNFQ1VSSVRZX0dST1VQX1JVTEU+PFBST1RPQ09MPjwhW0NEQVRBW0FMTF1dPjwvUFJPVE9DT0w+PFJVTEVfVFlQRT48IVtDREFUQVtPVVRCT1VORF1dPjwvUlVMRV9UWVBFPjxTRUNVUklUWV9HUk9VUF9JRD48IVtDREFUQVswXV0+PC9TRUNVUklUWV9HUk9VUF9JRD48U0VDVVJJVFlfR1JPVVBfTkFNRT48IVtDREFUQVtkZWZhdWx0XV0+PC9TRUNVUklUWV9HUk9VUF9OQU1FPjwvU0VDVVJJVFlfR1JPVVBfUlVMRT48L1RFTVBMQVRFPjxURU1QTEFURT48U0VDVVJJVFlfR1JPVVBfUlVMRT48UFJPVE9DT0w+PCFbQ0RBVEFbQUxMXV0+PC9QUk9UT0NPTD48UlVMRV9UWVBFPjwhW0NEQVRBW0lOQk9VTkRdXT48L1JVTEVfVFlQRT48U0VDVVJJVFlfR1JPVVBfSUQ+PCFbQ0RBVEFbMF1dPjwvU0VDVVJJVFlfR1JPVVBfSUQ+PFNFQ1VSSVRZX0dST1VQX05BTUU+PCFbQ0RBVEFbZGVmYXVsdF1dPjwvU0VDVVJJVFlfR1JPVVBfTkFNRT48L1NFQ1VSSVRZX0dST1VQX1JVTEU+PC9URU1QTEFURT48SElTVE9SWV9SRUNPUkRTPjxISVNUT1JZPjxIT1NUTkFNRT5ub2RlMy5mZWxkaG9zdC5jejwvSE9TVE5BTUU+PC9ISVNUT1JZPjwvSElTVE9SWV9SRUNPUkRTPjxISVNUT1JZX1JFQ09SRFM+PEhJU1RPUlk+PFZNX01BRD48IVtDREFUQVtrdm1dXT48L1ZNX01BRD48L0hJU1RPUlk+PC9ISVNUT1JZX1JFQ09SRFM+PFRFTVBMQVRFPjxOSUM+PEFSX0lEPjwhW0NEQVRBWzBdXT48L0FSX0lEPjxCUklER0U+PCFbQ0RBVEFbb25lYnI2XV0+PC9CUklER0U+PENMVVNURVJfSUQ+PCFbQ0RBVEFbMTAwXV0+PC9DTFVTVEVSX0lEPjxJUD48IVtDREFUQVsxMC40Ni4xLjExN11dPjwvSVA+PE1BQz48IVtDREFUQVswMjowMDowYToyZTowMTo3NV1dPjwvTUFDPjxNT0RFTD48IVtDREFUQVt2aXJ0aW9dXT48L01PREVMPjxORVRXT1JLPjwhW0NEQVRBW0ZlZWRvRGV2ZWxvcF1dPjwvTkVUV09SSz48TkVUV09SS19JRD48IVtDREFUQVs2XV0+PC9ORVRXT1JLX0lEPjxORVRXT1JLX1VOQU1FPjwhW0NEQVRBW2ZlbGRzYW1dXT48L05FVFdPUktfVU5BTUU+PE5JQ19JRD48IVtDREFUQVswXV0+PC9OSUNfSUQ+PFBIWURFVj48IVtDREFUQVt0ZWFtMF1dPjwvUEhZREVWPjxTRUNVUklUWV9HUk9VUFM+PCFbQ0RBVEFbMF1dPjwvU0VDVVJJVFlfR1JPVVBTPjxUQVJHRVQ+PCFbQ0RBVEFbb25lLTEzMjEtMF1dPjwvVEFSR0VUPjxWTEFOX0lEPjwhW0NEQVRBWzIwNl1dPjwvVkxBTl9JRD48Vk5fTUFEPjwhW0NEQVRBWzgwMi4xUV1dPjwvVk5fTUFEPjwvTklDPjwvVEVNUExBVEU+PC9WTT4=
Fri Sep 23 16:47:24 2016 [Z0][VMM][I]: /var/tmp/one/vnm/vlan.rb: /var/tmp/one/vnm/vlan.rb:80: Invalid next (SyntaxError)
Fri Sep 23 16:47:24 2016 [Z0][VMM][I]: ExitCode: 1
Fri Sep 23 16:47:24 2016 [Z0][VMM][I]: Failed to execute network driver operation: pre.
Fri Sep 23 16:47:24 2016 [Z0][VMM][E]: Error deploying virtual machine: 802.1Q: -

#4 Updated by Jaime Melis about 4 years ago

  • Status changed from Closed to Assigned
  • Resolution deleted (fixed)

You are very right... reopening.

#5 Updated by Jaime Melis about 4 years ago

  • Status changed from Assigned to Closed

Fixed again, can you test and reopen if it fails?

thanks!!

#6 Updated by Kristian Feldsam about 4 years ago

Hello, thank you. I tested, deploy works and also issue was fixed.

Also available in: Atom PDF