Bug #4911

Fix several issues in the migration process from 5.0 to 5.2

Added by OpenNebula Systems Support Team almost 4 years ago. Updated over 3 years ago.

Status:ClosedStart date:11/10/2016
Priority:NormalDue date:
Assignee:Javi Fontan% Done:

0%

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

Description

- Duplicated VM adds in state 6
- VNC ports for undeployed VMs not taken into account

[Check community forum for more issues]

opennebula-5.2.0-upgradelosesvnc.diff Magnifier (777 Bytes) Roy Keene, 12/14/2016 05:12 PM


Related issues

Related to Bug #4892: onedb upgrade fails due to inserting a duplicate key Closed 11/03/2016

History

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

#2 Updated by Ruben S. Montero almost 4 years ago

  • Related to deleted (Feature #4937: Database toolset enhancements )

#3 Updated by Ruben S. Montero almost 4 years ago

  • Related to Bug #4892: onedb upgrade fails due to inserting a duplicate key added

#4 Updated by Roy Keene almost 4 years ago

I ran into an issue upgrading to 5.2.0 with VNC ports, the below patch is what I used to work around the issue.

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

  • Assignee set to Javi Fontan

#6 Updated by Javi Fontan over 3 years ago

Fixed VNC port problem in this pull request:

https://github.com/OpenNebula/one/pull/214

#7 Updated by Javi Fontan over 3 years ago

  • Status changed from New to Closed
  • Resolution set to wontfix

#8 Updated by Javi Fontan over 3 years ago

  • Resolution changed from wontfix to fixed

Also available in: Atom PDF