[
https://issues.apache.org/jira/browse/CLOUDSTACK-6409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14100740#comment-14100740
]
Pierre-Luc Dion commented on CLOUDSTACK-6409:
---------------------------------------------
Could it be possible this issue has been resolved ?
> Upgrade from 4.2.1 to 4.3.0 failed due to database upgrade script
> -----------------------------------------------------------------
>
> Key: CLOUDSTACK-6409
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6409
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Upgrade
> Affects Versions: 4.3.0
> Environment: CentOS 6.4, MySQL
> Reporter: Yong Chen
> Labels: patch
>
> Upgrade failed due to SQL upgrade script for 421-to-430 tries to add many
> columns and tables that are exist already in 4.2.1.
> Tried to modify DB manually (see below SQL commands) to satisfy the upgrade
> script. However it seems there are a lot more than a few. This upgrade script
> needs to be reviewed to be able to detect existence of columns and tables or
> remove them if needed rather than fail.
> ALTER TABLE async_job CHANGE related session_key INT;
> ALTER TABLE async_job ADD job_cmd_originator INT;
> ALTER TABLE async_job ADD callback_type INT;
> ALTER TABLE async_job ADD callback_address INT;
> ALTER TABLE async_job DROP job_type;
> ALTER TABLE async_job DROP job_dispatcher;
> ALTER TABLE async_job DROP job_executing_msid;
> ALTER TABLE async_job DROP job_pending_signals;
> ALTER TABLE network_offerings DROP keep_alive_enabled;
> ALTER TABLE vm_instance DROP power_state;
> ALTER TABLE vm_instance DROP power_state_update_time;
> ALTER TABLE vm_instance DROP power_state_update_count;
> ALTER TABLE vm_instance DROP FOREIGN KEY fk_vm_instance__power_host;
> ALTER TABLE vm_instance DROP power_host;
> ALTER TABLE load_balancing_rules DROP lb_protocol;
> DROP TABLE vm_work_job;
> DROP TABLE async_job_journal;
> DROP TABLE async_job_join_map;
> ALTER TABLE configuration DROP default_value;
--
This message was sent by Atlassian JIRA
(v6.2#6252)
