cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] (CLOUDSTACK-9765) broken after upgrade
Date Tue, 31 Jan 2017 17:22:51 GMT


ASF GitHub Bot commented on CLOUDSTACK-9765:

GitHub user resmo opened a pull request:

    CLOUDSTACK-9765: centos: packaging: fix missing path in spec file

    Related to 6051fa503a2da7b96256f21e6b7c42aa1f3cb01e

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

    $ git pull fix/centos-spec-upgrade-db-properties

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

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

    This closes #1923
commit 5d51bb52ef108772f150384f54b6b43ab1cb3ff9
Author: Rene Moser <>
Date:   2017-01-31T17:15:12Z

    CLOUDSTACK-9765: centos: packaging: fix missing path in spec file post install


> broken after upgrade
> ----------------------------------
>                 Key: CLOUDSTACK-9765
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Upgrade
>    Affects Versions:
>            Reporter: René Moser
>            Assignee: René Moser
> {code}
> shapeblue0.el6.x86_64                                                               
>   Updating   : cloudstack-management-                  
> warning: /etc/cloudstack/management/ created as /etc/cloudstack/management/
> sed: can't read No such file or directory
> Unable to determine ssl settings for server.xml, please run cloudstack-setup-management
> Unable to determine ssl settings for tomcat.conf, please run cloudstack-setup-management
> {code}
> Seeing this error while installing the RPM, resulting in cloudstack management server
is not able to connect to the DB after MS service start

This message was sent by Atlassian JIRA

View raw message