Bug #1957

CLI --net_context fails if the user supplies an ID instead of a name

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

Status:ClosedStart date:04/25/2013
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:CLI
Target version:-
Resolution:invalid Pull request:
Affected Versions:OpenNebula 4.0

Description

This command

$ onetemplate create --name test --cpu 0.1 --memory 128 --nic 34 --net_context

Creates a valid NIC, but the CONTEXT uses 34 as the network name, not its ID

TEMPLATE CONTENTS                                                               
CONTEXT=[
  ETH0_CONTEXT_FORCE_IPV4="$NETWORK[CONTEXT_FORCE_IPV4, NETWORK=\"34\"]",
  ETH0_DNS="$NETWORK[DNS, NETWORK=\"34\"]",
  ETH0_GATEWAY="$NETWORK[GATEWAY, NETWORK=\"34\"]",
  ETH0_GATEWAY6="$NETWORK[GATEWAY6, NETWORK=\"34\"]",
  ETH0_IP="$NIC[IP, NETWORK=\"34\"]",
  ETH0_IPV6="$NIC[IP6_GLOBAL, NETWORK=\"34\"]",
  ETH0_MASK="$NETWORK[NETWORK_MASK, NETWORK=\"34\"]",
  ETH0_NETWORK="$NETWORK[NETWORK_ADDRESS, NETWORK=\"34\"]" ]
CPU="0.1" 
MEMORY="128" 
NIC=[
  NETWORK_ID="34" ]

It should be NETWORK_ID=\"34\" instead

History

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

  • Priority changed from Normal to Low

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

  • Priority changed from Low to Normal

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

  • Target version set to Release 4.2

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

  • Target version changed from Release 4.2 to Release 4.4

#5 Updated by Carlos Martín almost 8 years ago

  • Status changed from New to Closed
  • Target version deleted (Release 4.4)
  • Resolution set to invalid

Does not apply anymore, since 4.2 --net_context adds CONTEXT = [ NETWORK = YES ]

Also available in: Atom PDF