[jira] [Updated] (CLOUDSTACK-8041) 4.5.0 db upgrade fail if new systemvm templates are abscent

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Yadav updated CLOUDSTACK-8041: Fix Version/s: 4.6.0 4.5.0 4.5.0 db upgrade fail if new systemvm

[jira] [Commented] (CLOUDSTACK-8041) 4.5.0 db upgrade fail if new systemvm templates are abscent

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14236773#comment-14236773 ] Rohit Yadav commented on CLOUDSTACK-8041: - Can we have this kind of fix (cc

[jira] [Issue Comment Deleted] (CLOUDSTACK-8041) 4.5.0 db upgrade fail if new systemvm templates are abscent

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Yadav updated CLOUDSTACK-8041: Comment: was deleted (was: Can we have this kind of fix (cc [~dahn]): For each

[jira] [Commented] (CLOUDSTACK-8041) 4.5.0 db upgrade fail if new systemvm templates are abscent

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14236780#comment-14236780 ] Rohit Yadav commented on CLOUDSTACK-8041: - Went through the logs and upgrade

[jira] [Commented] (CLOUDSTACK-8041) 4.5.0 db upgrade fail if new systemvm templates are abscent

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14236814#comment-14236814 ] Pierre-Luc Dion commented on CLOUDSTACK-8041: - I'd like to avoid the need

[jira] [Commented] (CLOUDSTACK-8041) 4.5.0 db upgrade fail if new systemvm templates are abscent

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14236874#comment-14236874 ] Pierre-Luc Dion commented on CLOUDSTACK-8041: - This might be already

[jira] [Closed] (CLOUDSTACK-8041) 4.5.0 db upgrade fail if new systemvm templates are abscent

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion closed CLOUDSTACK-8041. --- Resolution: Invalid Look like upgrading from 4.3.0 require only one

[jira] [Updated] (CLOUDSTACK-8042) Fail to upgrade to 4.5.0 from 4.3.1

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion updated CLOUDSTACK-8042: Labels: upgrade (was: ) Fail to upgrade to 4.5.0 from 4.3.1

[jira] [Created] (CLOUDSTACK-8042) Fail to upgrade to 4.5.0 from 4.3.1

Pierre-Luc Dion created CLOUDSTACK-8042: --- Summary: Fail to upgrade to 4.5.0 from 4.3.1 Key: CLOUDSTACK-8042 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8042 Project: CloudStack

[jira] [Updated] (CLOUDSTACK-8042) Fail to upgrade to 4.5.0 from 4.3.1

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion updated CLOUDSTACK-8042: Attachment: management-server.log localhost.2014-12-06.log

[jira] [Commented] (CLOUDSTACK-6212) 'vm_instance' table has no AUTO_INCREMENT on 'id' field

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14236879#comment-14236879 ] ASF GitHub Bot commented on CLOUDSTACK-6212: Github user ke4qqq commented

[jira] [Updated] (CLOUDSTACK-8042) Fail to upgrade to 4.5.0 from 4.3.1

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley updated CLOUDSTACK-8042: - Priority: Blocker (was: Major) Fail to upgrade to 4.5.0 from 4.3.1