[
https://issues.apache.org/jira/browse/CLOUDSTACK-9489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15533174#comment-15533174
]
ASF GitHub Bot commented on CLOUDSTACK-9489:
--------------------------------------------
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1684
@pdion891 @jburwell as I've already explained, there should be no need to
enable dynamic apichecker if you're upgrading from an older system that has a
commands.properties file. I think the upgrade tests was performed not using
packages but maven/jetty. The current 4.9+ branch don't have
commands.properties so when you rebuild mgmt server you don't get the
commands.properties in the classpath. This has been documented in the admin
docs as well. If you've installed 4.9+ based mgmt server on a new server, the
old commands.properties file need to be copied to the new server to continue to
use the static checker, otherwise the dynamic checker need to be enabled and
migrated using a migration script as documented here:
http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.9/accounts.html#using-dynamic-roles
> 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)
