[
https://issues.apache.org/jira/browse/CLOUDSTACK-7814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14187707#comment-14187707
]
ASF subversion and git services commented on CLOUDSTACK-7814:
-------------------------------------------------------------
Commit 865b2e6791a37371fff4c43c974c90f44d24c418 in cloudstack's branch
refs/heads/4.5 from [~yasker]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=865b2e6 ]
CLOUDSTACK-7814: Fix default passphrase for keystores
In upgrade case, the db.properties file is not changed, but the following commit
would require passphrase for keystore in it, thus result in error(NPE in fact
due to there is no such properity).
commit 918c320438980f070150f872e3a3ba907572af83
Author: Upendra Moturi <[email protected]>
Date: Fri Jun 20 11:41:58 2014 +0530
CLOUDSTACK-6847.Link.java and console proxy files have hardcoded value
This commit fix it by put default value for passphrases, also set correct
passphrase if fail-safe keystore is used.
> 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 <[email protected]>
> 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)