cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9467) Fresh installation of cloudstack-usage server fails
Date Tue, 23 Aug 2016 11:58:20 GMT

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

ASF GitHub Bot commented on CLOUDSTACK-9467:
--------------------------------------------

GitHub user rhtyd opened a pull request:

    https://github.com/apache/cloudstack/pull/1657

    CLOUDSTACK-9467: Add symlink to key file for usage server

    On fresh installation, the usage server fails to start if the `key` file does
    not exist in its classpath. The issue is reproducible in environments (such as Trillian)
    where the usage server is installed before cloudstack-setup-databases has been called.
    Before the cloudstack db has been setup, the key file does not exist at its
    default location and installation of usage-server fails to add a symlink to the
    key file.
    
    This fix adds a default symlink to `/etc/cloudstack/management/key` if a
    symlink/file does not already exist in the /etc/cloudstack/usage directory.
    
    On new installation, in the post-installation steps it checks if the symlink
    or file exists, and adds a symlink if it does not exist. On existing
    installations, if symlink or file exists then it will skip adding symlink.
    
    /cc @jburwell @PaulAngus @karuturi 
    @blueorangutan package

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/shapeblue/cloudstack 4.8-usageserverfix

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1657.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1657
    
----
commit 8cd44b1684b41884f10f350318dc8130eb5b5f75
Author: Rohit Yadav <rohit.yadav@shapeblue.com>
Date:   2016-08-23T11:50:41Z

    CLOUDSTACK-9467: Add symlink to key file for usage server
    
    On fresh installation, the usage server fails to start if the `key` file does
    not exist in its classpath. The issue is reproducible in environments where
    the usage server is installed before cloudstack-setup-databases has been called.
    Before the cloudstack db has been setup, the key file does not exist at its
    default location and installation of usage-server fails to add a symlink to the
    key file.
    
    This fix adds a default symlink to `/etc/cloudstack/management/key` if a
    symlink/file does not already exist in the /etc/cloudstack/usage directory.
    
    On new installation, in the post-installation steps it checks if the symlink
    or file exists, and adds a symlink if it does not exist. On existing
    installations, if symlink or file exists then it will skip adding symlink.
    
    Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>

----


> 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)

Mime
View raw message