cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From borisroman <>
Subject [GitHub] cloudstack pull request: CLOUDSTACK-9046 - Fix upgrade path from 4...
Date Mon, 09 Nov 2015 16:34:31 GMT
Github user borisroman commented on the pull request:
    LGTM :+1: 
    Deployed 4.5.2 from DEB packages on Ubuntu 14.04. Deployed a zone, deployed the systemvm's
and spawned a uservm.
    Upgraded to 4.6 with packages build from this branch. Upgrade went ok! :+1: 
    INFO  [c.c.u.DatabaseUpgradeChecker] (main:null) DB version = 4.5.2 Code Version = 4.6.0
    INFO  [c.c.u.DatabaseUpgradeChecker] (main:null) Database upgrade must be performed from
4.5.2 to 4.6.0
    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 Upgrade452to460 to upgrade
from 4.5.2-4.6.0 to 4.6.0
    INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) Configuring CloudStack Components
    INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) Done Configuring CloudStack

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 or file a JIRA ticket
with INFRA.

View raw message