[
https://issues.apache.org/jira/browse/CLOUDSTACK-4645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13765335#comment-13765335
]
Kishan Kavala commented on CLOUDSTACK-4645:
-------------------------------------------
I was able to upgrade from 4.1.1 to 4.2.0 without any issues.
2013-09-12 16:03:40,013 DEBUG [utils.db.ScriptRunner] (Timer-2:null) -- END:
support for LXC
2013-09-12 16:03:40,014 DEBUG [utils.db.ScriptRunner] (Timer-2:null) CREATE
TABLE `cloud`.`vm_snapshots` ( `id` bigint(20) unsigned NOT NULL
auto_increment COMMENT 'Primary Key', `uuid` varchar(40) NOT NULL, `name`
varchar(255) NOT NULL, `display_name` varchar(255) default NULL,
`description` varchar(255) default NULL, `vm_id` bigint(20) unsigned NOT
NULL, `account_id` bigint(20) unsigned NOT NULL, `domain_id` bigint(20)
unsigned NOT NULL, `vm_snapshot_type` varchar(32) default NULL, `state`
varchar(32) NOT NULL, `parent` bigint unsigned default NULL, `current`
int(1) unsigned default NULL, `update_count` bigint unsigned NOT NULL DEFAULT
0, `updated` datetime default NULL, `created` datetime default NULL,
`removed` datetime default NULL, PRIMARY KEY (`id`), CONSTRAINT UNIQUE KEY
`uc_vm_snapshots_uuid` (`uuid`), INDEX `vm_snapshots_name` (`name`), INDEX
`vm_snapshots_vm_id` (`vm_id`), INDEX `vm_snapshots_account_id`
(`account_id`), INDEX `vm_snapshots_display_name` (`display_name`), INDEX
`vm_snapshots_removed` (`removed`), INDEX `vm_snapshots_parent` (`parent`),
CONSTRAINT `fk_vm_snapshots_vm_id__vm_instance_id` FOREIGN KEY
`fk_vm_snapshots_vm_id__vm_instance_id` (`vm_id`) REFERENCES `vm_instance`
(`id`), CONSTRAINT `fk_vm_snapshots_account_id__account_id` FOREIGN KEY
`fk_vm_snapshots_account_id__account_id` (`account_id`) REFERENCES `account`
(`id`), CONSTRAINT `fk_vm_snapshots_domain_id__domain_id` FOREIGN KEY
`fk_vm_snapshots_domain_id__domain_id` (`domain_id`) REFERENCES `domain` (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8
2013-09-12 16:03:40,173 DEBUG [utils.db.ScriptRunner] (Timer-2:null) ALTER
TABLE `cloud`.`hypervisor_capabilities` ADD COLUMN `vm_snapshot_enabled`
tinyint(1) DEFAULT 0 NOT NULL COMMENT 'Whether VM snapshot is supported by
hypervisor'
> There is no upgrade path from 4.1.1 to 4.2.0
> --------------------------------------------
>
> Key: CLOUDSTACK-4645
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4645
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup
> Affects Versions: 4.2.0
> Reporter: Milamber
> Assignee: Venkata Siva Vijayendra Bhamidipati
> Priority: Blocker
>
> I've try to upgrade my CS test platform from 4.1.1 to 4.2.0
> (from Commit: e39a7d8e0d3f2fd3e326b1bdf4aaf9ba5d900b02
> + CLVM issue cherry-pick from 4.2-forward with commitId
> f2c5b5fbfe45196dfad2821fca513ddd6efa25c9.)
> The path 4.1.1->4.2.0 seems miss?
> 2013-09-11 14:32:55,619 INFO [cloud.upgrade.DatabaseUpgradeChecker]
> (Timer-1:null) Grabbing lock to check for database upgrade.
> 2013-09-11 14:32:55,631 INFO [cloud.upgrade.DatabaseUpgradeChecker]
> (Timer-1:null) DB version = 4.1.1 Code Version = 4.2.0
> 2013-09-11 14:32:55,632 INFO [cloud.upgrade.DatabaseUpgradeChecker]
> (Timer-1:null) Database upgrade must be performed from 4.1.1 to 4.2.0
> 2013-09-11 14:32:55,632 ERROR [cloud.upgrade.DatabaseUpgradeChecker]
> (Timer-1:null) There is no upgrade path from 4.1.1 to 4.2.0
> 2013-09-11 14:32:55,639 ERROR [utils.component.ComponentContext]
> (Timer-1:null) System integrity check failed. Refuse to startup
> com.cloud.utils.exception.CloudRuntimeException: There is no upgrade path
> from 4.1.1 to 4.2.0
> at
> com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:221)
> at
> com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:389)
> 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)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
