cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Burwell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9489) When upgrading, Config.java new configuration are not updated.
Date Sat, 03 Sep 2016 15:59:20 GMT

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

John Burwell commented on CLOUDSTACK-9489:
------------------------------------------

[~pdion] Requiring a database to running and properly configured as part of package post-installation
is against best packaging practices for both Debian and Red Hat/Fedora.  If we were to change
this value, it seems more appropriate to do it as part of the DatabaseUpgradeChecker.

[~rohit.yadav@shapeblue.com] [~widodh] do you know of any reason why we don't set this value
as part of the database upgrade?

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