Bug #188

ONE CLI should check syntax

Added by Tino Vázquez about 11 years ago. Updated over 9 years ago.

Status:ClosedStart date:01/19/2010
Priority:NormalDue date:
Assignee:Carlos Martín% Done:

0%

Category:-
Target version:Release 3.0
Resolution:wontfix Pull request:
Affected Versions:

Description

Otherwise, it leads to syntax errors. Or maybe the core should check this since the XMLRPC API is also prone to this errors.

From Daniel Morán Jiménez <>
--
Hello,

I'm using OpenNebula 1.4, and I have found that a misspelling on the network_address parameter in a template leads to a crash of the whole application (either creating the new network with the onevnet command or using an XMLRPC call). Deploying this template:

NAME = "private"
TYPE = RANGED
BRIDGE = eth1
NEWORK_ADDRESS = 10.95.240.0
NETWORK_SIZE = 2046

throws this error: "Error: end of file reached". Subsequent ONE commands or XMLRPC connections throw the error: "Error: Connection refused - connect(2)", so the server must be restarted. Once restarted, a onevnet list command shows there is a vnet called "private", but every command issued with its id throws an "Error getting Virtual Network with NID = 30" so it can't be deleted. I have found a workaround to get rid of this network, by creating another one with the same name and deleting it, but I don't have any idea what is going internally, and this sollution doesn't seem to be a good idea :) (is the network being overriden or is the old one lost in the Limbo?). Shouldn't the syntax be checked before processing the commands to prevent further errors?

Best regards
Daniel Moran

Associated revisions

Revision ab5aac46
Added by Javi Fontan about 4 years ago

Merge pull request #188 from vholer/master

Install all Gems deps when using bundler. Ubuntu 16.10 Gemfile.lock

History

#1 Updated by Ruben S. Montero almost 11 years ago

  • Assignee set to Tino Vázquez
  • Target version set to Release 1.4.2

#2 Updated by Ruben S. Montero over 10 years ago

  • Status changed from New to Assigned

this is a problem in drop (with the lease object)

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

  • Assignee changed from Tino Vázquez to Carlos Martín
  • Target version changed from Release 1.4.2 to Release 3.0

Part of this bug was solved for 2.0 series (daemon crash). However the OpenNebula core should check that all the needed attributes has been specified (for each resource VM, Network, Image...). I am scheduling this issue to 2.4

#4 Updated by Ruben S. Montero over 9 years ago

  • Status changed from Assigned to Closed
  • Resolution set to wontfix

We'll rely on the core parser engine to ease the implementation of multiple bindings. Now the core returns the error and the line.

Also available in: Atom PDF