Bug 624281

Summary: reporting via abrt fails since BZ upgrade to 3.6
Product: [Community] Bugzilla Reporter: Patrick C. F. Ernzer <pcfe>
Component: Creating/Changing BugsAssignee: David Lawrence <dkl>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: 3.6CC: kbaker, nelhawar
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-17 16:17:02 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:
Attachments:
Description Flags
v1 for adding mapping to statuswhiteboard field dkl: review+

Description Patrick C. F. Ernzer 2010-08-15 15:47:26 UTC 
Description of problem:
tried submitting a bug via abrt (GUI and CLI) today but it fails as per the below.

Version-Release number of selected component (if applicable):
bugzilla 3.6
abrt-1.1.1-2.fc13.x86_64

How reproducible:
could reproduce twice in a row, once via GUI, once via CLI

Steps to Reproduce:
1. something crashes, abrt shows icon
2. abrt-cli --get-list
3. abrt-cli --report <some ID>
  
Actual results:
Report using Bugzilla? [y/N]: y
Wrong settings were detected for plugin Bugzilla.
Enter your login: pcfe
Enter your password: 
>> Logging into bugzilla...
>> Checking for duplicates...
>! XML-RPC Fault(32000): RPC failed at server.  There is a problem with your search: statuswhiteboard is not a valid field name. The legal field names are listed here.
>> Reporting via 'Bugzilla' was not successful: XML-RPC Fault(32000): RPC failed at server.  There is a problem with your search: statuswhiteboard is not a valid field name. The legal field names are listed here.
Bugzilla: XML-RPC Fault(32000): RPC failed at server.  There is a problem with your search: statuswhiteboard is not a valid field name. The legal field names are listed here.


Expected results:
bug submitted to bugzilla via abrt

Additional info:
Up until Friday I was able to report bugs through abrt on this machine to bugzilla just fine.
Bug 623983 is the last bug I successfully reported to bugzilla through abrt (2010-08-13 06:54 EDT)
Comment 1 David Lawrence 2010-08-16 04:02:26 UTC 
I was hoping that the beta's would flesh out these type of issues. Can someone provide the exact XMLRPC call that is being used that is causing the error and the params that are being passed? It is possible that a field name has changed fomr version 3.4 to 3.6 and we will need to put in a workaround.

Dave
Comment 2 Patrick C. F. Ernzer 2010-08-16 11:58:42 UTC 
I think the owner of abrt might be a better target for needinfo.

I'm not sure how to extract the xmlrpc call abrt does. As it's SSL traffic to bugzilla, tcpdumping will not help me.
Comment 3 Noura El hawary 2010-08-17 11:43:59 UTC 
Created attachment 439091 [details]
v1 for adding mapping to statuswhiteboard field

Hi,

looking at the error message posted in the previous comments seems that user is performing a search using the parameter statuswhiteboard, in 3.4 we had mapping of statuswhiteboard => status_whiteboard which is missing in 3.6, attached is a patch for that missing mapping. 

This patch is based on the assumption that the error is coming from the xmlrpc search function.

Cheers,
Noura
Comment 4 Kevin Baker 2010-08-17 14:02:13 UTC 
Is this mapping maintained by us or by the upstream. If so, please get it patched upstream. One less thing to bite us on the next upgrade.
Comment 5 David Lawrence 2010-08-17 15:17:32 UTC 
Comment on attachment 439091 [details]
v1 for adding mapping to statuswhiteboard field

Thanks Noura. I will go ahead and check this in so if I push another update today it will go in.

Dave
Comment 6 David Lawrence 2010-08-17 16:17:02 UTC 
Checked in and will be in the next code update.
Comment 7 Noura El hawary 2010-08-18 12:07:05 UTC 
(In reply to comment #4)
> Is this mapping maintained by us or by the upstream. If so, please get it
> patched upstream. One less thing to bite us on the next upgrade.

Hi Kevin, yes the mapping is maintained by upstream I submitted the patch upstream.

Cheers,
Noura