Bug #5405

Erase vnc port and wild mapping entry when you delete a vm

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

Status:ClosedStart date:09/26/2017
Priority:NormalDue date:
Assignee:Juan Jose Montiel Cano% Done:

0%

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

Description

When you do a 'onevm recover --delete <vid>' ,OpenNebula doesn't erase the vnc port and when you try to use the port with other vm, vnc reports an error.

Associated revisions

Revision beae0776
Added by Juan Jose Montiel Cano over 3 years ago

B #5405: unified functionality for free vm resources in a single function (#498)

Revision fe65615f
Added by Juan Jose Montiel Cano over 3 years ago

B #5405: unified functionality for free vm resources in a single function (#498)

(cherry picked from commit beae0776c344334d3503529751aab8a1e75915ea)

History

#1 Updated by Ruben S. Montero over 3 years ago

  • Subject changed from Erase vnc port when you delete a vm to Erase vnc port and wild mapping entry when you delete a vm
  • Status changed from Pending to Closed
  • Resolution set to fixed

Also available in: Atom PDF