Bug #4911
Fix several issues in the migration process from 5.0 to 5.2
| Status: | Closed | Start date: | 11/10/2016 | |
|---|---|---|---|---|
| Priority: | Normal | Due 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 
(777 Bytes)
Related issues
History
#1
Updated by Ruben S. Montero over 4 years ago
- Related to Feature #4937: Database toolset enhancements added
#2
Updated by Ruben S. Montero over 4 years ago
- Related to deleted (Feature #4937: Database toolset enhancements )
#3
Updated by Ruben S. Montero over 4 years ago
- Related to Bug #4892: onedb upgrade fails due to inserting a duplicate key added
#4
Updated by Roy Keene over 4 years ago
- File opennebula-5.2.0-upgradelosesvnc.diff added
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 about 4 years ago
- Assignee set to Javi Fontan
#6
Updated by Javi Fontan almost 4 years ago
Fixed VNC port problem in this pull request:
#7
Updated by Javi Fontan almost 4 years ago
- Status changed from New to Closed
- Resolution set to wontfix
#8
Updated by Javi Fontan almost 4 years ago
- Resolution changed from wontfix to fixed