1388330 - Balrog updater for Thunderbird fails with BAD REQUEST

Status: RESOLVED DUPLICATE of bug 1389312

(Release Engineering :: Release Automation, enhancement)

Description

[Mihai Tabara [:mtabara]⌚️GMT]

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.

Comment 1

[Mihai Tabara [:mtabara]⌚️GMT]

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

[Nick Thomas [:nthomas] (UTC+12)]

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

[Nick Thomas [:nthomas] (UTC+12)]

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.

Comment 4

[Nick Thomas [:nthomas] (UTC+12)]

https://bugzilla.mozilla.org/show_bug.cgi?id=1389312#c1 could well be relevant.

Comment 5

[Mihai Tabara [:mtabara]⌚️GMT]

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.

Comment 6

[Nick Thomas [:nthomas] (UTC+12)]

Fixed by bug 1389312.