Bug 1022760

Summary: Occasional Exception when adding a project maintainer
Product: [Retired] Zanata Reporter: Damian Jansen <djansen>
Component: Component-LogicAssignee: zanata-dev-internal <zanata-dev-internal>
Status: CLOSED WORKSFORME QA Contact: Zanata-QA Mailling List <zanata-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.0CC: aeng, djansen, zanata-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-28 05:48:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Test run log file none

Description Damian Jansen 2013-10-24 00:42:55 UTC
Created attachment 815593 [details]
Test run log file

Description of problem:
Occasionally an exception will occur when pressing add and close on the Add Maintainer dialog

Version-Release number of selected component (if applicable):
3.x

How reproducible:
Difficult, occasional

Steps to Reproduce:
1. Sign in as admin, go to a project
2. Press Manage Maintainers
3. Press Add Maintainer
4. Enter a maintainer name
5. Click the autocomplete
6. Click somewhere to populate the fields
7. Press Add
8. Press Close

Actual results:
Exception:
org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [org.zanata.model.HProject#1]

Expected results:
No exception.

Additional info:
Run log attached

Comment 1 Alex Eng 2014-06-18 03:09:51 UTC
Is this issue still occurring in 3.4.x?

Comment 2 Damian Jansen 2014-07-28 05:48:10 UTC
As of 3.5.0-SNAPSHOT (git-server-3.4.2-201-ge0afdde) - it appears not.