cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-10269) Allow deletion of roles without causing concurrent exception
Date Fri, 09 Feb 2018 10:55:01 GMT

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

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

Commit 0befb2cceb8e2634adf796cd99ed89342ad03bf3 in cloudstack's branch refs/heads/master from
[~rohithsharma]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=0befb2c ]

CLOUDSTACK-10269: On deletion of role set name to null (#2444)

During deletion of role, set name to null. This fixes concurrent
exception issue where previously it would rename the deleted role
with a timestamp.

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

> Allow deletion of roles without causing concurrent exception
> ------------------------------------------------------------
>
>                 Key: CLOUDSTACK-10269
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10269
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Rohit Yadav
>            Assignee: Rohit Yadav
>            Priority: Major
>             Fix For: Future, 4.11.1.1, 4.12.0.0
>
>
> Deletion of a role renames the role with a timestamp, when roles are created/deleted
aggresively it may cause concurrent exceptions. The fix is to follow how other cloudstack
entities are removed where name uniqueness need to be honoured, i.e. by setting the field
to null. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message