Bug #757

Sunstone VNC does not set deploy hostname correctly

Added by Hector Sanjuan almost 10 years ago. Updated almost 10 years ago.

Status:ClosedStart date:07/29/2011
Priority:HighDue date:
Assignee:Hector Sanjuan% Done:

100%

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

Description

As VMs deploy HOSTNAME is now under HISTORY_RECORDS instead of HISTORY, sunstone server fails to find it, and launches the VNC proxy with the wrong parameters.

Associated revisions

Revision dfd49018
Added by Hector Sanjuan almost 10 years ago

Bug #757: Fix: start vnc proxy setup

Fixed the access to the Hostname in which the VM is deployed. Improved proxy start by calling direcly the proxy script and not the launch.sh wrapper script.

History

#1 Updated by Hector Sanjuan almost 10 years ago

  • % Done changed from 0 to 100
  • Resolution set to fixed

fixed on feature-746 branch.

#2 Updated by Hector Sanjuan almost 10 years ago

  • Status changed from New to Closed

Also available in: Atom PDF