Bug #5356

After importing wild VM with an unavailable VNC por it throws an error but the VM is stuck in HOLD

Added by Jaime Melis about 3 years ago. Updated about 3 years ago.

Status:ClosedStart date:09/08/2017
Priority:NormalDue date:
Assignee:Sergio Semedi% Done:

0%

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

Description

Steps to reproduce:

  • Import wild VM from vCenter
  • Clone VM in vCenter
  • Import the clone wild VM from vCenter
  • VM is in hold state

Another way of reproducing it (although not tested) would be:

  • Create a new KVM VM using a VNC port that is in use in OpenNebula
  • Import wild VM

The expected behaviour is:

  • When importing a cloned VM from vCenter, the VNC port should be remove (if it's an OpenNebula clone)
  • If it can be imported, the VM should be deleted, not kept in HOLD

Associated revisions

Revision d6d266b5
Added by Sergio Semedi about 3 years ago

B #5356: (vcenter) core crash on hold hotfix (#526)

Revision 29533341
Added by Sergio Semedi about 3 years ago

B #5356: (vcenter) core crash on hold hotfix (#526)

(cherry picked from commit d6d266b5bf79b3ed237402c4f3d7d715515330ab)

History

#1 Updated by Jaime Melis about 3 years ago

When importing a cloned VM from vCenter, the VNC port should be remove (if it's an OpenNebula clone)

Meaning, if it has opennebula.* fields in the vmx (extraconfig), they should be ignored, so a new port can be assigned

#2 Updated by Sergio Semedi about 3 years ago

  • Assignee set to Sergio Semedi

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

  • Tracker changed from Backlog to Bug
  • Category changed from Drivers - VM to Core & System
  • Status changed from Pending to Closed
  • Target version changed from Release 5.6 to Release 5.4.3
  • Affected Versions OpenNebula 5.4, OpenNebula 5.4.1, OpenNebula 5.4.2 added

Also available in: Atom PDF