Bug 813647

Summary: Stacktrace when closing a bug
Product: [Community] Bugzilla Reporter: Krzysztof Daniel <kdaniel>
Component: Creating/Changing BugsAssignee: Simon Green <sgreen>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.2CC: ebaak, mbenitez, sgreen, vdanen
Target Milestone: 4.2-1   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.2.0-0.b26 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-04-20 05:00:39 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 786624    

Description Krzysztof Daniel 2012-04-18 06:22:04 UTC
I have observed this behaviour when using Eclipse Mylyn.

(1) Install eclipse and eclipse-mylyn-*
(2) Open any bug that is on QA state.
(3) Try to move it to 'CLOSED'
(4) Error appears that indicates bugzilla error:

(Eclipse says) Error may result when QAContact field not enabled.
((Embedded browser shows)
 Undef to trick_taint at Bugzilla/Util.pm line 67
       Bugzilla::Util::trick_taint('undef') called at Bugzilla/Bug.pm line
 4525
       Bugzilla::Bug::LogActivityEntry(766608, 'cf_last_closed', 'undef',
 '2012-04-17 07:22:48', 324097, '2012-04-17 07:22:48') called
 at ./extensions/RedHat/Extension.pm line 992
 
 ugzilla::Extension::RedHat::bug_end_of_update('Bugzilla::Extension::RedHat=HASH(0xa930c0)', 'HASH(0xe243760)') called at Bugzilla/Hook.pm line 33
       Bugzilla::Hook::process('bug_end_of_update', 'HASH(0xe243760)') called
 at Bugzilla/Bug.pm line 1157
       Bugzilla::Bug::update('Bugzilla::Bug=HASH(0xddf60d0)') called
 at /var/www/html/bugzilla/process_bug.cgi line 498

Comment 1 Simon Green 2012-04-18 11:13:45 UTC
I noticed this a few hours before you filed the bug. It applies to all cases where you close a bug for the first time. Will get it fixed tomorrow hopefully.

Comment 2 Simon Green 2012-04-18 21:45:34 UTC
*** Bug 813927 has been marked as a duplicate of this bug. ***

Comment 3 Simon Green 2012-04-20 05:00:39 UTC
Fix will be visible in the next update

  -- simon