Bug #323
Same XML-RPC machine state for several onevm state
| Status: | Closed | Start date: | 08/23/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Tino Vázquez |
% Done: | 0% |
|
| Category: | Client API & Library | |||
| Target version: | - | |||
| Resolution: | worksforme | Affected Version: | ||
| Story points | - | |||
| Velocity based estimate | - |
Description
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.
History
Updated by Martin Kopta over 1 year ago
Did you check LCM_STATE?
Updated by Alexandre Joseph over 1 year 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 :-)
Updated by Ruben S. Montero over 1 year ago
- Status changed from New to Closed
- Resolution set to worksforme