Bug #5360
VXLAN driver error in 5.4
| Status: | Closed | Start date: | 09/12/2017 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | - | |||
| Resolution: | duplicate | Pull request: | ||
| Affected Versions: | OpenNebula 5.4 |
Description
Tue Sep 12 05:01:42 2017 [Z0][VMM][D]: Message received: LOG I 212 /var/tmp/one/vnm/vxlan/vxlan_driver.rb:54:in `create_vlan_dev': uninitialized constant VNMMAD::VNMNetwork::IPv4 (NameError) Tue Sep 12 05:01:42 2017 [Z0][VMM][D]: Message received: LOG I 212 from /var/tmp/one/vnm/vlan.rb:56:in `block in activate' Tue Sep 12 05:01:42 2017 [Z0][VMM][D]: Message received: LOG I 212 from /var/tmp/one/vnm/vnm_driver.rb:78:in `call' Tue Sep 12 05:01:42 2017 [Z0][VMM][D]: Message received: LOG I 212 from /var/tmp/one/vnm/vnm_driver.rb:78:in `block in process' Tue Sep 12 05:01:42 2017 [Z0][VMM][D]: Message received: LOG I 212 from /var/tmp/one/vnm/vm.rb:61:in `call' Tue Sep 12 05:01:42 2017 [Z0][VMM][D]: Message received: LOG I 212 from /var/tmp/one/vnm/vm.rb:61:in `block in each_nic' Tue Sep 12 05:01:42 2017 [Z0][VMM][D]: Message received: LOG I 212 from /var/tmp/one/vnm/vm.rb:60:in `each' Tue Sep 12 05:01:42 2017 [Z0][VMM][D]: Message received: LOG I 212 from /var/tmp/one/vnm/vm.rb:60:in `each_nic' Tue Sep 12 05:01:42 2017 [Z0][VMM][D]: Message received: LOG I 212 from /var/tmp/one/vnm/vnm_driver.rb:81:in `process' Tue Sep 12 05:01:42 2017 [Z0][VMM][D]: Message received: LOG I 212 from /var/tmp/one/vnm/vlan.rb:38:in `activate' Tue Sep 12 05:01:42 2017 [Z0][VMM][D]: Message received: LOG I 212 from /var/tmp/one/vnm/vxlan/pre:30:in `<main>' Tue Sep 12 05:01:42 2017 [Z0][VMM][D]: Message received: LOG I 212 ExitCode: 1 Tue Sep 12 05:01:42 2017 [Z0][VMM][D]: Message received: LOG I 212 Failed to execute network driver operation: pre.
It was working prior to version 5.4.
Related issues
History
#1
Updated by Ruben S. Montero almost 4 years ago
- Status changed from Pending to Closed
- Resolution set to duplicate
#2
Updated by Ruben S. Montero almost 4 years ago
- Duplicates Bug #5302: VXLAN driver is using a module that does not exist added
#3
Updated by Alvaro Simon almost 4 years ago
I got the same issue, the fix is already available in the master branch, I did this workaround https://forum.opennebula.org/t/solved-vxlan-driver-error-in-opennebula-5-4/4931 and it is working now.