You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Sheng Yang (JIRA)" <ji...@apache.org> on 2014/10/29 00:30:35 UTC

[jira] [Resolved] (CLOUDSTACK-7814) No default SSL keystore result in upgrade failure

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

Sheng Yang resolved CLOUDSTACK-7814.
------------------------------------
    Resolution: Fixed

> No default SSL keystore result in upgrade failure
> -------------------------------------------------
>
>                 Key: CLOUDSTACK-7814
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7814
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.5.0
>            Reporter: Sheng Yang
>            Assignee: Sheng Yang
>            Priority: Blocker
>             Fix For: 4.5.0
>
>
> Currently, after upgrade to 4.5, no agent can connect to mgmt server.
> It's due to:
> commit 918c320438980f070150f872e3a3ba907572af83
> Author: Upendra Moturi <up...@sungard.com>
> Date: Fri Jun 20 11:41:58 2014 +0530
> CLOUDSTACK-6847.Link.java and console proxy files have hardcoded value
> This commit meant to use more flex password for keystore, but they didn't set default value for it. So when upgrade, db.properities which suppose have the password is empty, the decryption of SSL keystore would fail.



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