[
https://issues.apache.org/jira/browse/CLOUDSTACK-9489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15533219#comment-15533219
]
ASF GitHub Bot commented on CLOUDSTACK-9489:
--------------------------------------------
Github user jburwell commented on the issue:
https://github.com/apache/cloudstack/pull/1684
@rhtyd discussing this issue with @paul, there is a scenario where this
wedged condition can occur. If you perform an upgrade by creating a new
management server VM then no commands.properties file will be present and the
dynamic API checker will be set to off. This upgrade approach is taken as a
best practice to provide a simple, reliable rollback strategy and an
opportunity to perform OS upgrades. I think the solution in this situation is
combination of improved upgrade documentation (i.e. copy over your
commands.properties or run the import script and turn on the dynamic role API
checker) and some better error messages that will help admins understand how to
remedy the problem.
> 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)
