[
https://issues.apache.org/jira/browse/CLOUDSTACK-8562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15288850#comment-15288850
]
ASF GitHub Bot commented on CLOUDSTACK-8562:
--------------------------------------------
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.
> User Definable Roles
> --------------------
>
> Key: CLOUDSTACK-8562
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8562
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Reporter: Paul Angus
> Assignee: Rohit Yadav
>
> Static command.properties moved to database and made user definable
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
