Bug #1927

VM Context does not fill the right values when a VM has two NICs in the same network

Added by Carlos Martín about 8 years ago. Updated almost 5 years ago.

Status:ClosedStart date:04/18/2013
Priority:LowDue date:
Assignee:-% Done:

0%

Category:Core & System
Target version:-
Resolution:duplicate Pull request:
Affected Versions:OpenNebula 4.0

Description

The VM context uses the NETWORK name to differentiate NICs, e.g.

CONTEXT = [
  ETH0_IP = "$NIC[IP, NETWORK=\"public\"]",
  ETH1_IP = "$NIC[IP, NETWORK=\"private\"]" 
]

But when two NICs use the same network, both context attributes resolve to the first IP.

Maybe this could be fixed using NIC_ID.

Related issues

Related to Backlog #2029: Make context packages use the whole template instead of u... Closed 05/13/2013
Related to Backlog #3784: IP(v6) alias(es) support Pending 04/30/2015

History

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

  • Target version deleted (Release 4.2)

#2 Updated by Ruben S. Montero about 8 years ago

  • Priority changed from Normal to Low

#3 Updated by Ruben S. Montero almost 5 years ago

  • Status changed from New to Closed
  • Resolution set to duplicate

This needs support from OpenNebula core. Closing as this is a missing feature

#4 Updated by Ruben S. Montero almost 5 years ago

Also available in: Atom PDF