[
https://issues.apache.org/jira/browse/CLOUDSTACK-9467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15434273#comment-15434273
]
ASF GitHub Bot commented on CLOUDSTACK-9467:
--------------------------------------------
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1657
@jburwell no this is PR is related to packaging, while 1593 fixes something
different. The Travis build failure has been fixed at #1648, the failures are
unrelated to this PR. Since this is a packaging fix, built packages confirm
that packaging is not broken. Further, Trillian tests confirm regression
testing (though due to an infra issue the tests have not been commented here).
Manual installation confirmed the fix, usage server started without any
issue.
># /etc/init.d/cloudstack-usage status
> * cloudstack-usage is running
> Fresh installation of cloudstack-usage server fails
> ---------------------------------------------------
>
> Key: CLOUDSTACK-9467
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9467
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Rohit Yadav
> Assignee: Rohit Yadav
> Priority: Blocker
> Fix For: 4.10.0, 4.9.1, 4.8.2
>
>
> On fresh installation of cloudstack, the key file is not symlinked to the
> /etc/cloudstack/management/key file causing the usage server to fail to start:
> Caused by: com.cloud.utils.exception.CloudRuntimeException: key File
> containing secret key not found in the classpath:
> at
> com.cloud.utils.crypt.EncryptionSecretKeyChecker.check(EncryptionSecretKeyChecker.java:83)
> at com.cloud.utils.db.DbProperties.getDbProperties(DbProperties.java:80)
> at
> com.cloud.utils.db.TransactionLegacy.<clinit>(TransactionLegacy.java:999)
> The fix is to add a symlink.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
