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-9489) When upgrading, Config.java new configuration are not updated.
Date Thu, 29 Sep 2016 17:25:20 GMT

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

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

Github user rhtyd commented on the issue:

    https://github.com/apache/cloudstack/pull/1684
  
    @PaulAngus but it's up to the admin and how they want to upgrade/setup a new mgmt server.
Assuming you want to create a new mgmt server for each old mgmt server, one strategy could
be to copy the commands.properties from each old mgmt server to each such new mgmt server.


> When upgrading, Config.java new configuration are not updated.
> --------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9489
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9489
>             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/Config.java}}
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
(v6.3.4#6332)

Mime
View raw message