[jira] [Commented] (CLOUDSTACK-10052) Upgrading to 4.9.2 causes confusion/issues around dynamic roles usage

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-10052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16136496#comment-16136496 ] 

ASF subversion and git services commented on CLOUDSTACK-10052:
--------------------------------------------------------------

Commit 310195cbe25ac49160713e511d75525a16c9364b in cloudstack's branch refs/heads/4.9 from [~bhaisaab]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=310195c ]

CLOUDSTACK-10052: Simplify dynamic roles enable checking (#2241)

This fixes issue of enabling dynamic roles based on the global setting
only. This also fixes application of the default role/permissions mapping
on upgrade from 4.8 and previous versions to 4.9+.

Previously, it would make additional check to ensure commands.properties
is not in the classpath however this creates confusion for admins who
may skip/skim through the rn/docs and assume that mere changing the
global settings was not enough.

Signed-off-by: Rohit Yadav <ro...@shapeblue.com>

> Upgrading to 4.9.2 causes confusion/issues around dynamic roles usage
> ---------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-10052
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10052
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.9.2.0
>            Reporter: Rohit Yadav
>            Assignee: Rohit Yadav
>             Fix For: 4.11.0.0, 4.9.3.0
>
>
> The dynamic roles feature need to be enabled based on the global setting only, the additional check to disable it when commands.properties is in the classpath is not widely known and causes issue on freshly installed system.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)