Bug 1098730

Summary: dynflow task locks are left after updating user via api
Product: Red Hat Satellite Reporter: Tom McKay <tomckay>
Component: InfrastructureAssignee: Ivan Necas <inecas>
Status: CLOSED CURRENTRELEASE QA Contact: Tazim Kolhar <tkolhar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.3CC: cwelton, inecas, jmontleo, omaciel, tkolhar
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/5778
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-02 14:06:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tom McKay 2014-05-17 19:12:00 UTC
  id  |               task_id                |    name    | resource_type | resou
rce_id | exclusive 
------+--------------------------------------+------------+---------------+------
-------+-----------
 5654 | 8d06d9b6-7f26-4585-b7b0-386b68c1999a | task_owner | User          |      
     1 | f
 5655 | 8d06d9b6-7f26-4585-b7b0-386b68c1999a | read       | User          |      
    65 | t
 5656 | 8d06d9b6-7f26-4585-b7b0-386b68c1999a | write      | User          |      
    65 | t

After updating users via api, there are many locks in foreman_tasks_locks table.

Comment 1 Tom McKay 2014-05-17 19:12:02 UTC
Created from redmine issue http://projects.theforeman.org/issues/5778

Comment 3 Ivan Necas 2014-05-19 14:21:07 UTC
Proposed fix at https://github.com/theforeman/foreman-tasks/pull/53

Comment 5 Ivan Necas 2014-05-27 13:50:58 UTC
Fixed in https://github.com/theforeman/foreman-tasks/pull/53 and released in foreman-tasks-0.5.5

Comment 7 Tazim Kolhar 2014-06-26 07:14:01 UTC
VERIFIED

Comment 8 Bryan Kearney 2014-07-02 14:06:26 UTC
This was delivered with 6.0.3, which is the Satellite 6 Beta.