772142 - 400 Bad Request /allizom/ instance for simple query that works on /latest/

Status: RESOLVED WONTFIX

(Webtools Graveyard :: BzAPI, defect)

Description

[Carl Meyer (:carljm)]

I have a small tool that scrapes issues from BzAPI and Github and dumps them into a common CSV format, for use by b2g project management.

In testing this tool with the new 4.2 Bugzilla instance, when I query this URL: https://api-dev.bugzilla.mozilla.org/allizom/bug?cf_blocking_basecamp=%2B

I get a 400 Bad Request response with the message "Unknown Bugzilla error. Title: 'Parameters Required'"

But the production version of my tool is making the same query, https://api-dev.bugzilla.mozilla.org/latest/bug?cf_blocking_basecamp=%2B and that works as expected.

Comment 1

[:glob ✱]

the blocking_basecamp flag was added to bmo after may 14 (bug 758797 - may 29), so it isn't present on bugzilla.allizom.org.

bugzilla.allizom.org is returning "parameters required" because it's seeing bzapi's request as one without any parameters.

this bug is most probably invalid, although i'm not sure what bzapi's expected behaviour is when it is passed invalid fields.

Comment 2

[Gervase Markham [:gerv]]

BzAPI translates:

https://api-dev.bugzilla.mozilla.org/allizom/bug?cf_blocking_basecamp=%2B

into

https://bugzilla.allizom.org/buglist.cgi?cf_blocking_basecamp=%2B&columnlist=all&ctype=csv

which Bugzilla interprets as a search without search terms, because it doesn't know the field name. Given that BzAPI doesn't have exhaustive knowledge of all custom field names (if it did, it would need updating each time we created a new one), I think this behaviour is fine.

Gerv