cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohit Yadav (JIRA)" <>
Subject [jira] [Closed] (CLOUDSTACK-10249) Improve dynamic roles upgrade paths
Date Tue, 23 Jan 2018 20:19:00 GMT


Rohit Yadav closed CLOUDSTACK-10249.
    Resolution: Fixed

Dupes CLOUDSTACK-10236, Closing.

> Improve dynamic roles upgrade paths
> -----------------------------------
>                 Key: CLOUDSTACK-10249
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Rohit Yadav
>            Assignee: Rohit Yadav
>            Priority: Blocker
>             Fix For:
> A 4.5 env upgraded to 4.11 fails to let admin log in. The issue is resolved by adding
`quotaIsEnabled=15` in file. The aim of this ticket is to handle this
issue in three parts:
>  * Include notes in release notes about how to use dynamic roles post upgrade, handle
changes in file
>  * If file is missing, and global setting for dynamic role is disable,
enable that. This may be done in the 4.8->4.9 Java based upgrade path code. Doing this
will ensure only 4.8 and previous env when upgraded to 4.11 will receive such a change.
>  * The dynamic role python basd migration script can have a new flag to have the defaults
accepted as set by the upgrade, this script will only change global setting when the flag
is passed without reading any file.

This message was sent by Atlassian JIRA

View raw message