cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9489) When upgrading, new configuration are not updated.
Date Thu, 29 Sep 2016 17:17:20 GMT


ASF GitHub Bot commented on CLOUDSTACK-9489:

Github user rhtyd commented on the issue:
    @jburwell when a fresh mgmt server is deployed for upgrading an existing CloudStack environment,
several files from `/etc/cloudstack/management` are copied to the new server, especially the
`` file. The `` is no different, in the past all such deployment
(where in-place upgrades were avoided) copied all these config files in /etc/cloudstack/management
from old server to new server.
    Official docs only talk about in-place upgrades, our packaging system (post-install/upgrade
scripts) assume in-place upgrade as well; if someone's doing fresh mgmt server for upgrade,
they know what they are doing and its out-of-scope of what the project can support. At the
same time, we may add documentation for such kind of upgrades as well. The solution for this
problem is documentation and release/upgrade notes.

> When upgrading, new configuration are not updated.
> --------------------------------------------------------------
>                 Key: CLOUDSTACK-9489
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.6.2, 4.7.1, 4.8.0, 4.9.0
>            Reporter: Pierre-Luc Dion
>            Assignee: Pierre-Luc Dion
>            Priority: Blocker
> When Upgrading CloudStack, new configurations (Global Settings) defined in  {{server/src/com/cloud/configuration/}}
are not populated.
> This file changed in 4.5 and 4.6 and those configurations are not applied when upgrading
to post 4.6.

This message was sent by Atlassian JIRA

View raw message