[
https://issues.apache.org/jira/browse/CLOUDSTACK-5992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14090570#comment-14090570
]
Rohit Yadav commented on CLOUDSTACK-5992:
-----------------------------------------
Hari, what are you trying to do here? Is this still applicable?
config params are expected to be null if not inserted, no? I saw the patch, it
just changes alert.wait and adds component to VO in ConfigDepotImpl
> [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)
