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

ASF GitHub Bot commented on CLOUDSTACK-10269:
---------------------------------------------

rhtyd opened a new pull request #2444: CLOUDSTACK-10269: On deletion of role 
set name to null
URL: https://github.com/apache/cloudstack/pull/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.
   
   Pinging for review - @DaanHoogland @nvazquez @borisstoyanov and others.
   
   @blueorangutan package

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


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

Reply via email to