cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhinandan Prateek (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-4999) [upgrade]Upgrade from 4.2 to 4.2.1 failed with message "There is no upgrade path from 4.2.0 to 4.2.1-SNAPSHOT"
Date Wed, 30 Oct 2013 08:11:34 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Abhinandan Prateek updated CLOUDSTACK-4999:
-------------------------------------------

    Assignee: Kishan Kavala

> [upgrade]Upgrade from 4.2 to 4.2.1 failed with message "There is no upgrade path from
4.2.0 to 4.2.1-SNAPSHOT"
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4999
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4999
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Upgrade
>    Affects Versions: 4.2.1
>         Environment: upgrade from 4.2 to 4.2.1 with KVM host 
>            Reporter: manasaveloori
>            Assignee: Kishan Kavala
>            Priority: Blocker
>             Fix For: 4.2.1
>
>         Attachments: management-server.zip
>
>
> 1.Have CS with 4.2 build on RHEL62 .
> 2. Add KVM6.2  .
> 3. Have some VMs deployed using isolated/VPC networks.
> 4.Configure LB,portfowording,static NAT rules..
> 5.Do an upgrade to 4.2.1
> Observed the following error message in logs:
> Running SystemIntegrityChecker DatabaseUpgradeChecker
> 2013-10-30 17:37:23,020 INFO  [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:null) Grabbing
lock to check for database upgrade.
> 2013-10-30 17:37:23,029 DEBUG [upgrade.dao.VersionDaoImpl] (Timer-2:null) Checking to
see if the database is at a version before it was the version table is created
> 2013-10-30 17:37:23,041 INFO  [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:null) DB
version = 4.2.0 Code Version = 4.2.1-SNAPSHOT
> 2013-10-30 17:37:23,041 INFO  [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:null) Database
upgrade must be performed from 4.2.0 to 4.2.1-SNAPSHOT
> 2013-10-30 17:37:23,045 ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:null) There
is no upgrade path from 4.2.0 to 4.2.1-SNAPSHOT
> 2013-10-30 17:37:23,053 ERROR [utils.component.ComponentContext] (Timer-2:null) System
integrity check failed. Refuse to startup
> com.cloud.utils.exception.CloudRuntimeException: There is no upgrade path from 4.2.0
to 4.2.1-SNAPSHOT
>         at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:224)
>         at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:392)
>         at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:90)
>         at com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54)
>         at java.util.TimerThread.mainLoop(Timer.java:534)
>         at java.util.TimerThread.run(Timer.java:484)
> Attaching the MS logs.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message