Bug #5465

Not Reseale vnc port when stop the virtual machine

Added by Juan Jose Montiel Cano about 3 years ago. Updated about 3 years ago.

Status:ClosedStart date:10/18/2017
Priority:NormalDue date:
Assignee:Juan Jose Montiel Cano% Done:

100%

Category:Core & System
Target version:Release 5.4.3
Resolution:fixed Pull request:
Affected Versions:OpenNebula 5.4, OpenNebula 5.4.1, OpenNebula 5.4.2

Description

If you stop a virtual machine, opennebula release vnc port of vm and when the vm has been resume,the port has changed

Associated revisions

Revision ff731e8e
Added by Ruben S. Montero about 3 years ago

B #5465: Do not free VNC ports on STOP and do not reassgin them on
resume

Revision 6f4cf6d0
Added by Ruben S. Montero about 3 years ago

B #5465: Do not free VNC ports on STOP and do not reassgin them on
resume

(cherry picked from commit ff731e8e5d3ed9a42a7826bc309db75ce262f768)

Revision 04b55718
Added by Ruben S. Montero about 3 years ago

B #5465: Fix history record check while getting VNC port

Revision db6d72a7
Added by Ruben S. Montero about 3 years ago

B #5465: Fix history record check while getting VNC port

(cherry picked from commit 04b557188fdf1dab72c46e8d94a9e1da94dde0c5)

Revision 56339a50
Added by Ruben S. Montero about 3 years ago

B #5465: Do not free VNC ports on STOP and do not reassgin them on
resume

Revision 01d062e7
Added by Ruben S. Montero about 3 years ago

B #5465: Fix history record check while getting VNC port

(cherry picked from commit 04b557188fdf1dab72c46e8d94a9e1da94dde0c5)

History

#1 Updated by Juan Jose Montiel Cano about 3 years ago

  • % Done changed from 0 to 100

#2 Updated by Ruben S. Montero about 3 years ago

  • Status changed from Pending to Closed
  • Resolution set to fixed

Also available in: Atom PDF