[
https://issues.apache.org/jira/browse/CLOUDSTACK-6378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13965457#comment-13965457
]
Sheng Yang commented on CLOUDSTACK-6378:
----------------------------------------
We traced back the issue to:
commit de448ec4792eda5b47d79b26e9cb8ce96a2b22f4
Author: Wei Zhou <w.z...@leaseweb.com>
Date: Thu Nov 7 11:09:06 2013 +0100
CLOUDSTACK-5042: change cloud.keystore to cloudmanagementserver.keystore
and install it
This commit only modify the keystore name, but remain the real place to use the
keystore unchangd. It would make cloudstack fail to found the keystore when
"cloud.keystore" not existed, thus involve in fail-safe keystore kick in.
We're working on fix it.
> SSL: Fail to find the generated keystore.
> -----------------------------------------
>
> Key: CLOUDSTACK-6378
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6378
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.2.1, 4.3.0
> Environment: Confirmed this is an issue on centos 6.5 and ubuntu
> 12.04 on both versions of Cloudstack 4.2.1 and 4.3.0
> Reporter: Michael Phillips
> Priority: Minor
>
> The logs on versions 4.2.1 and 4.3.0 get filled with the following error:
> WARN [c.c.u.n.Link] (AgentManager-Selector:null) SSL: Fail to find the
> generated keystore. Loading fail-safe one to continue.
> In 4.2.1, the fix was to rename cloudmanagementserver.keystore, to
> cloud.keystore then restart cloudstack.
> In 4.3.0, the system by default does not create the file named
> cloudmanagementserver.keystore. You now have to create the keystore file by
> running "sudo keytool -genkey -keystore", then name the file cloud.keystore.
> This error is reproducible, and confirmed by other users.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
