[
https://issues.apache.org/jira/browse/CLOUDSTACK-5992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14091159#comment-14091159
]
Harikrishna Patnala commented on CLOUDSTACK-5992:
-------------------------------------------------
I'm trying to remove the inconsistency on default values and component names on
fresh setup and upgraded setup.
UPDATE `cloud`.`configuration` SET `default_value` = `value`;
Above sql query runs during upgrade and copies value to default_value, but this
is not happening for fresh setup since configparams are accumulated from
ConfigurationServer during MS start.
My change "configVO.setDefaultValue(value);" fixes the setting up default value
on fresh setup. (check the change in
server/src/com/cloud/server/ConfigurationServerImpl.java in the same patch)
> [Upgrade] default values of configuraiton parameters in configuration table
> are set NULL on fresh setup
> --------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-5992
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5992
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Upgrade
> Affects Versions: 4.3.0
> Reporter: Harikrishna Patnala
> Assignee: Harikrishna Patnala
> Fix For: 4.4.0
>
> Attachments: ConfigPropertiesComparison.html
>
>
> During recent Upgrade test,
> 1) many of the global parameters have NULL values as the default Values.
> 2) Component names are different in fresh and upgrade setup
> I attached the comparison document to this
--
This message was sent by Atlassian JIRA
(v6.2#6252)
