Github user remibergsma commented on the pull request:
https://github.com/apache/cloudstack/pull/1072#issuecomment-158053349
LGTM, did an upgrade from `4.4.4` to `4.6.1-SNAPSHOT` and that worked now
with only the `4.6` template registered. This was done with XenServer.
```
INFO [c.c.u.DatabaseUpgradeChecker] (main:null) DB version = 4.4.4 Code
Version = 4.6.1-SNAPSHOT
INFO [c.c.u.DatabaseUpgradeChecker] (main:null) Database upgrade must be
performed from 4.4.4 to 4.6.1-SNAPSHOT
WARN [c.c.u.d.Upgrade452to460] (main:null) 4.6.0LXC SystemVm template not
found. LXC hypervisor is not used, so not failing upgrade
WARN [c.c.u.d.Upgrade452to460] (main:null) 4.6.0Hyperv SystemVm template
not found. Hyperv hypervisor is not used, so not failing upgrade
WARN [c.c.u.d.Upgrade452to460] (main:null) 4.6.0Ovm3 SystemVm template not
found. Ovm3 hypervisor is not used, so not failing upgrade
WARN [c.c.u.d.Upgrade452to460] (main:null) 4.6.0VMware SystemVm template
not found. VMware hypervisor is not used, so not failing upgrade
WARN [c.c.u.d.Upgrade452to460] (main:null) 4.6.0KVM SystemVm template not
found. KVM hypervisor is not used, so not failing upgrade
INFO [c.c.u.DatabaseUpgradeChecker] (main:null) Cleaning upgrades because
all management server are now at the same version
INFO [c.c.u.DatabaseUpgradeChecker] (main:null) Cleanup upgrade
Upgrade444to450 to upgrade from 4.4.4-4.5.0 to 4.5.0
INFO [c.c.u.DatabaseUpgradeChecker] (main:null) Cleanup upgrade
Upgrade450to451 to upgrade from 4.5.0-4.5.1 to 4.5.1
INFO [c.c.u.DatabaseUpgradeChecker] (main:null) Cleanup upgrade
Upgrade451to452 to upgrade from 4.5.1-4.5.2 to 4.5.2
INFO [c.c.u.DatabaseUpgradeChecker] (main:null) Cleanup upgrade
Upgrade452to460 to upgrade from 4.5.2-4.6.0 to 4.6.0
INFO [c.c.u.DatabaseUpgradeChecker] (main:null) Cleanup upgrade
Upgrade460to461 to upgrade from 4.6.0-4.6.1 to 4.6.1
```
Thanks @DaanHoogland let's find another reviewer and merge this to 4.6.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
