Red Hat Bugzilla – Bug 826305
Problem when making a comment while changing the status
Last modified: 2014-10-12 18:48:32 EDT
Description of problem:
Error message occurs when changing the status from ON_QA to ASSIGNED while making a comment.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Find a JBoss SOA 5 bug with the status of ON_QA
2. Change the status to assigned and make a comment.
3. Bugzilla go boom!
DBD::mysql::db do failed: Duplicate entry '4704854' for key 1 [for Statement "INSERT INTO longdescs (thetext, bug_id, work_time, comment_id, extra_data, who, bug_when, isprivate, already_wrapped, type) VALUES (?,?,?,?,?,?,?,?,?,?)"] at Bugzilla/Object.pm line 587
Bugzilla::Object::insert_create_data('Bugzilla::Comment', 'Bugzilla::Comment=HASH(0x12733730)') called at Bugzilla/Bug.pm line 1097
Bugzilla::Bug::update('Bugzilla::Bug=HASH(0x1224b800)') called at ./extensions/RedHat/Extension.pm line 1082
Bugzilla::Extension::RedHat::bug_end_of_update('Bugzilla::Extension::RedHat=HASH(0x11ecfcd0)', 'HASH(0x12733a40)') called at Bugzilla/Hook.pm line 33
Bugzilla::Hook::process('bug_end_of_update', 'HASH(0x12733a40)') called at Bugzilla/Bug.pm line 1198
Bugzilla::Bug::update('Bugzilla::Bug=HASH(0x1224b800)') called at /var/www/html/bugzilla/process_bug.cgi line 505
Comment made and status changed.
This may happen with other status changes for other products. The case above is the one that I can reproduce.
This will be fixed in the next release.
The error occurred when ALL the following are true.
1) The bug was in the state ON_QA, VERIFIED, or RELEASE_PENDING.
2) The bug was changed to the ASSIGNED state.
3) The bug did not have the FailedQA verified field set.
4) The user making the change has the ability to set the FailedQA verified field
5) A comment was made.
The temporary work around is to not do all those things at once :)
*** Bug 826371 has been marked as a duplicate of this bug. ***