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
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
