Bug #963

User object may not be unlocked by the RM

Added by Carlos Martín over 9 years ago. Updated over 9 years ago.

Status:ClosedStart date:11/04/2011
Priority:NormalDue date:
Assignee:Carlos Martín% Done:

0%

Category:Core & System
Target version:Release 3.2
Resolution:fixed Pull request:
Affected Versions:OpenNebula 3.0

Description

RequestManagerUser::request_execute locks the User object and passes it to the corresponding user_action method.
If an xmlrpc_c exception is raised inside this method, it is not catched and the User is left locked.

Associated revisions

Revision ba91887f
Added by Carlos Martín over 9 years ago

Bug #963: RequestManagerUser checks the parameter types before the User object is locked

Revision f41a20d4
Added by Ruben S. Montero over 9 years ago

Bug #963: Prevents seg fault if user is freed while executing RM action

Revision a3ef9891
Added by Carlos Martín over 9 years ago

Bug #963: Solve lock issue in RM (cherry picked from ba91887f & f41a20d4)

History

#1 Updated by Ruben S. Montero over 9 years ago

  • Target version changed from Release 3.4 to Release 3.2

#2 Updated by Ruben S. Montero over 9 years ago

  • Status changed from New to Assigned
  • Assignee set to Carlos Martín

#3 Updated by Ruben S. Montero over 9 years ago

  • Status changed from Assigned to Closed
  • Resolution set to fixed

Also available in: Atom PDF