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

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

GitHub user abhinandanprateek opened a pull request:

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

    CLOUDSTACK-9489: the new config vars that are added do not goto DB if…

    … values are set to NULL, removing this check so the entries in DB are made 
with NULL values

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

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

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

    https://github.com/apache/cloudstack/pull/1684.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 #1684
    
----
commit a39cc61fc61a52b5d57e963a9a6a2d6f0e951c28
Author: Abhinandan Prateek <abhinandan.prat...@shapeblue.com>
Date:   2016-09-23T05:28:11Z

    CLOUDSTACK-9489: the new config vars that are added do not goto DB if 
values are set to NULL, removing this check so the entries in DB are made with 
NULL values

----


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

Reply via email to