Closed
Bug 1388330
Opened 7 years ago
Closed 7 years ago
Balrog updater for Thunderbird fails with BAD REQUEST
Categories
(Release Engineering :: Release Automation: Other, enhancement)
Release Engineering
Release Automation: Other
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1389312
People
(Reporter: mtabara, Unassigned)
References
Details
(Whiteboard: [releaseduty])
Not sure if this is a fallback from signoffs or something else. This is still on BB-automation so I'm not sure we've done the switch there as well.
Reporter | ||
Comment 1•7 years ago
|
||
More details in log[1] from builder[2]. [1]: http://buildbot-master73.bb.releng.usw2.mozilla.com:8001/builders/release-comm-beta-update_shipping_beta/builds/4/steps/run_script/logs/stdio [2]: http://buildbot-master70.bb.releng.use1.mozilla.com:8001/builders/release-comm-beta-update_shipping_beta
Comment 2•7 years ago
|
||
Needs to submit a signoff rather than a old-style rule change: Caught HTTPError: {"status": 400, "exception": "This change requires signoff, it cannot be done directly. No Signoffs given", "type": "about:blank", "detail": "SignoffRequiredError", "title": "Bad Request"}
Comment 3•7 years ago
|
||
Hit this on 56.0b2 too, it's a general problem. Workaround is to manually schedule a change and chase for someone else for a signoff.
Summary: Balrog updater for Thunderbird 56.0b1 fails with BAD REQUEST → Balrog updater for Thunderbird fails with BAD REQUEST
Comment 4•7 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1389312#c1 could well be relevant.
Reporter | ||
Comment 5•7 years ago
|
||
Hit this on 56.0b3 too, it's a general problem. Workaround is to manually schedule a change and chase for someone else for a signoff.(In reply to Nick Thomas [:nthomas] from comment #3) > Hit this on 56.0b2 too, it's a general problem. Workaround is to manually > schedule a change and chase for someone else for a signoff. Same in 56.0b3.
Reporter | ||
Updated•7 years ago
|
Whiteboard: [releaseduty]
Comment 6•7 years ago
|
||
Fixed by bug 1389312.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•