[ https://issues.apache.org/jira/browse/CLOUDSTACK-9489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15531480#comment-15531480 ]
ASF GitHub Bot commented on CLOUDSTACK-9489: -------------------------------------------- Github user pdion891 commented on the issue: https://github.com/apache/cloudstack/pull/1684 Thanks @rhtyd, @jburwell @abhinandanprateek for the clarifications. Look like doing the ``update cloud.configuration set value='true' where name='dynamic.apichecker.enabled';`` fixe the authentication issue. Should we expect another issue post upgrade because of this db change? should we roll it back later? I haven't found the file command.properties when running 4.9.1.0-SNAPSHOT via jetty in the repo. also, in the context a user did customized some values, will they be reset? Thanks! > 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)