Bug #323

Same XML-RPC machine state for several onevm state

Added by Alexandre Joseph almost 11 years ago. Updated almost 11 years ago.

Status:ClosedStart date:08/23/2010
Priority:NormalDue date:
Assignee:Tino Vázquez% Done:


Category:Client API & Library
Target version:-
Resolution:worksforme Pull request:
Affected Versions:


When using OpenNebula XML-RPC API, it seems that the API always return a machine state equal to 3 when a machine is in the boot, prologue and running state.
Using the onevm tool, it is possible to get the real state but not with the XML-RPC API. Therefore, there is no way to know if the machine is really running or not.

Associated revisions

Revision c318f04f
Added by Javi Fontan about 4 years ago

Merge pull request #323 from vholer/feature-4977

F #4977: DB patch to clean MarketPlace Appliances


#1 Updated by Martin Kopta almost 11 years ago

Did you check LCM_STATE?

#2 Updated by Alexandre Joseph almost 11 years ago

Sorry, I've created this ticket before I get a response on how machine states works (#322). You're right, I have to check LCM_STATE when STATE equal 3.
You can close this ticket :-)

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

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

Also available in: Atom PDF