Closed
Bug 1415649
Opened 7 years ago
Closed 7 years ago
KeyError when a rule doesn't match an updateQuery that doesn't contain the SYSTEM_CAPABILITIES fields
Categories
(Release Engineering Graveyard :: Applications: Balrog (backend), enhancement, P1)
Release Engineering Graveyard
Applications: Balrog (backend)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: bhearsum)
References
Details
Attachments
(1 file)
While doing some verifications for Firefox 57.0 we ended up querying URLs such as: https://aus5.mozilla.org/update/3/Firefox/56.0.1/20171002220106/WINNT_x86-msvc-x86/be/release-localtest/Windows_NT%2010.0.0.0%20(x86)/default/default/update.xml?force=1 These are somewhat invalid update URLs (we never have clients in the wild that use /update/3 and 56.0.1), but this as uncovered a small bug in the backend where "instructionSet", "memory", and "jaws" aren't available on the updateQuery when we try to access them at https://github.com/mozilla/balrog/blob/8304c3ed1dc0e9f3c2df28d6035d144171cfb332/auslib/db.py#L1789
Assignee | ||
Comment 1•7 years ago
|
||
We seem to be hitting this in the wild with Avast queries, eg: https://aus5.mozilla.org/update/3/Firefox/56.0/20170831165232/WINNT_x86-msvc/en-US/release/Windows_NT%206.2.9200%20(x64)/default/default/update.xml?avast=1&force=1.
Priority: -- → P1
Assignee | ||
Comment 2•7 years ago
|
||
This is breaking updates for at least some Avast users, I'm going to get this fixed ASAP.
Assignee: nobody → bhearsum
Comment 3•7 years ago
|
||
Updated•7 years ago
|
Attachment #8932521 -
Flags: review+
Comment 4•7 years ago
|
||
Commit pushed to master at https://github.com/mozilla/balrog https://github.com/mozilla/balrog/commit/8347fadc70eb0c751745762856c038503f45ab44 bug 1415649: KeyError when a rule doesn't match an updateQuery that doesn't contain the SYSTEM_CAPABILITIES fields (#451). r=rail
Assignee | ||
Comment 5•7 years ago
|
||
This is in production, and eliminated the exceptions we were getting there.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•4 years ago
|
Product: Release Engineering → Release Engineering Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•