Github user rhtyd commented on the pull request:

    https://github.com/apache/cloudstack/pull/1489#issuecomment-220005496
  
    @anshul1886 okay, let's debug;
    - After you mvn re-built cleanly, did you run mvn deploydb?
    - If yes, what is the output of: select * from configuration where 
name='dynamic.apichecker.enabled'\G;
    For a fresh/clean install, the `value` should be 'true'.
    - Do you see any rules in cloud.role_permissions table for admin user 
(role_id=1). Default root admins (or account created using the default root 
admin role) are allowed all APIs. Are you using CloudStack as a non-root admin?
    - Check that there is no `commands.properties` file in the classpath for 
dynamic-roles to work. None of the apichecker will work if you've a 
commands.properties file in classpath but have dynamic.apichecker.enabled set 
to true. Try git clean -fdx to get rid of non-tracked files, or do a `find` and 
remove commands.properties file.
    - Check role_id column in cloud.accounts table, it should be `1` for root 
admin accounts. If it's NULL, something went wrong with the upgrade path.
    - Check errors on why the APIs are failing are you seeing, open Chrome 
dev-tools etc and share the results. Also check api/mgmt server logs.


---
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.
---

Reply via email to