Bug #1838

Sunstone: states with vnc access are not consistent

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

Status:ClosedStart date:03/27/2013
Priority:NormalDue date:
Assignee:Daniel Molina% Done:

100%

Category:Sunstone
Target version:Release 4.0
Resolution:fixed Pull request:
Affected Versions:OpenNebula 4.0

Description

The client shows the vnc icon for SHUTDOWN_POWEROFF, but the server returns "VM is not running".

Associated revisions

Revision e7d13c08
Added by Daniel Molina almost 8 years ago

bug #1838: states with vnc access are now consistent

Revision 7d5bdda0
Added by Daniel Molina almost 8 years ago

bug #1838: Check VNC states in sunstone server

Revision ddd4e724
Added by Daniel Molina almost 8 years ago

bug #1838: Use strings instead of integer in VNC_STATES

History

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

  • Assignee set to Tino Vázquez

#2 Updated by Daniel Molina almost 8 years ago

  • Status changed from New to Closed
  • Assignee changed from Tino Vázquez to Daniel Molina
  • % Done changed from 0 to 100
  • Resolution set to fixed

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

  • Status changed from Closed to New
  • Target version deleted (Release 4.0)
  • Resolution deleted (fixed)

Still fails to start the vnc session on 'shutdown' state. Seems to be this code in OpenNebulaVNC.rb

        if vm_resource['LCM_STATE'] != "3" 
            return error(400,"VM is not running")
        end

#4 Updated by Daniel Molina almost 8 years ago

  • Status changed from New to Closed
  • Target version set to Release 4.0
  • Resolution set to fixed

Also available in: Atom PDF