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

2014-12-08 Thread Rohit Yadav (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237685#comment-14237685
 ] 

Rohit Yadav commented on CLOUDSTACK-8042:
-

I see that the DB upgrade went fine, but during that some duplicate keys in 
Configuration were probably introduced causing:
2014-12-06 11:06:30,015 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) 
Caught exception when inserting system account: Duplicate entry '1' for key 
'PRIMARY'
2014-12-06 11:06:30,016 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) 
Caught SQLException when inserting system user: Duplicate entry '1' for key 
'PRIMARY'
2014-12-06 11:06:30,016 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) 
Caught SQLException when creating admin account: Duplicate entry '2' for key 
'PRIMARY'
2014-12-06 11:06:30,017 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) 
Caught SQLException when inserting admin user: Duplicate entry '2' for key 
'PRIMARY'

And a missing table?
2014-12-06 11:06:30,018 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) 
Caught (SQL?)Exception: no network_group  Table 'cloud.network_group' doesn't 
exist

Other than this a decryption error when mgmt server started and tried to make 
connections with the agent.


> 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
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.5.0
>Reporter: Pierre-Luc Dion
>Priority: Blocker
>  Labels: upgrade
> Attachments: catalina.out, localhost.2014-12-06.log, 
> management-server.log
>
>
> Fail to upgrade the management-server from 4.3.1 to 4.5.0. 
> The management-server is not working anymore after a direct upgrade from 
> 4.3.1 -> 4.5.0-rc1



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


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

2014-12-15 Thread David Nalley (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14246918#comment-14246918
 ] 

David Nalley commented on CLOUDSTACK-8042:
--

Is this still an issue? 

> 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
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.5.0
>Reporter: Pierre-Luc Dion
>Priority: Blocker
>  Labels: upgrade
> Attachments: catalina.out, localhost.2014-12-06.log, 
> management-server.log
>
>
> Fail to upgrade the management-server from 4.3.1 to 4.5.0. 
> The management-server is not working anymore after a direct upgrade from 
> 4.3.1 -> 4.5.0-rc1



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


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

2014-12-15 Thread Rohit Yadav (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14247867#comment-14247867
 ] 

Rohit Yadav commented on CLOUDSTACK-8042:
-

[~pdion] can confirm. I tested upgrading last week and found a related blocker 
upgrading from 4.3.1->4.3.2->4.4.0->4.4.2->4.5.0 and fixed it here: 
https://issues.apache.org/jira/browse/CLOUDSTACK-8070

> 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
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.5.0
>Reporter: Pierre-Luc Dion
>Priority: Blocker
>  Labels: upgrade
> Attachments: catalina.out, localhost.2014-12-06.log, 
> management-server.log
>
>
> Fail to upgrade the management-server from 4.3.1 to 4.5.0. 
> The management-server is not working anymore after a direct upgrade from 
> 4.3.1 -> 4.5.0-rc1



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)