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.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
