Bug 697292 - TCMS - nitrate xmlrpc: unacceptable format and size of NitrateXmlrpcError exception
Summary: TCMS - nitrate xmlrpc: unacceptable format and size of NitrateXmlrpcError exc...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: TCMS
Classification: Other
Component: Application
Version: 3.4
Hardware: Unspecified
OS: Linux
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Yuguang Wang
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-17 14:43 UTC by Max Benenson
Modified: 2011-06-16 08:45 UTC (History)
7 users (show)

Fixed In Version: 3.4.1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-16 08:45:07 UTC


Attachments (Terms of Use)
custom log file (8.20 MB, application/octet-stream)
2011-04-17 14:43 UTC, Max Benenson
no flags Details

Description Max Benenson 2011-04-17 14:43:38 UTC
Created attachment 492706 [details]
custom log file

Description of problem:
An attempt to write the caught NitrateXmlrpcError exception to the log file, dumps into it around 8MB of gibberish. Such format of the exception message is unacceptable since it's very hard to find something meaningful in such error message.

Steps to Reproduce:
1. For example, try to create twice a TestCaseRun with the same TestCase id using Nitrate xmlrpc
  
Actual results:
See attached log file

Expected results:
Should provide laconic message in the exception's body about the cause of the failure.

Additional info:
NOTE: this is a general issue, the same behavior on another minor failures.

Comment 1 Yuguang Wang 2011-05-05 10:06:04 UTC
hi Max,

It's known issue. I guess you're running rpc on stage server, we setup an instance on tcms-stage.englab.bne.redhat.com with debug mode thus generate so much exception message.
On product server, this won't occur.

I'll fix it later. Tons of error message is not acceptable.

Comment 2 Max Benenson 2011-05-05 11:25:41 UTC
(In reply to comment #1)
> hi Max,
> 
> It's known issue. I guess you're running rpc on stage server, we setup an
> instance on tcms-stage.englab.bne.redhat.com with debug mode thus generate so
> much exception message.
> On product server, this won't occur.
> 
> I'll fix it later. Tons of error message is not acceptable.

I will appreciate if you can give a highest priority to this task and handle it ASAP since I have to test our code on your stage server first (before I switch to the production) and right now such exceptions flood our log file and it's simply impossible to debug and find something meaningful in the log. Maybe as a temporary workaround I can pass a boolean flag to the server during login action (Auth.login_krbv) and this flag will indicate to disable the debug mode? Thank you

Comment 3 Yuguang Wang 2011-05-10 06:29:51 UTC
Hi Max,

Sure, will fix it within this week.
If everything goes well, the stage server will be updated within this week.

Comment 4 Yuguang Wang 2011-05-12 10:32:52 UTC
hey Max,

It's fixed, the debug mode of the rpc on stage server is disabled.
Please try it.

Comment 5 Jin Zhao 2011-06-10 08:52:04 UTC
Verify version 3.4.1-2 on englab/stage/engineering
Can not reproduce this issue now.

Comment 6 Xin Gao 2011-06-16 08:44:38 UTC
Additional info:

Verify version 3.4.1 on stage
Now situation is as follows,
When create twice a TestCaseRun with the same TestCase id
using Nitrate xmlrpc, Command line would prompt like: "xmlrpclib.Fault: <Fault 1: 'IntegrityError: (1062, "Duplicate entry..."

Verify result: PASS.


Note You need to log in before you can comment on or make changes to this bug.