1599223 - remove target.bz2.complete.mar from esr68

Status: RESOLVED FIXED

(Release Engineering :: Release Automation: Updates, task)

Description

[Aki Sasaki (not active)]

During the GCP migration, we moved from the signing servers to autograph, and have retired the signing servers. We appear to have missed target.bz2.complete.mar on esr68, which we explicitly pointed at the signing servers.

Let's remove target.bz2.complete.mar from our release graph. If needed, we should create a watershed so bz2 users get the previous release and then update from there.

Comment 1

[Aki Sasaki (not active)]

aki:foxkehdance-1: 12:05
will we need to create a watershed?
tom.prince:house: 12:09
@aki Nah, that already. The code still exists to allow us to make that watershed as late as possible. It turns out we didn't actually need it, since we needed a 60 watershed for a11y(?) related balrog checks anyway.
*already exsts
If we hadn't needed that 60 watershed, we could have updated people directly 52->68, which is what that code exists to support.

No new watershed needed.

Comment 2

[Aki Sasaki (not active)]

Attachment: Bug 1599223 - remove target.bz2.complete.mar r=tomprince a=release

Comment 3

[Aki Sasaki (not active)]

Attachment: Bug 1599223 - remove target.bz2.complete.mar r=tomprince

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/9805fb607886
remove target.bz2.complete.mar r=tomprince

Comment 5

[Aki Sasaki (not active)]

Comment on attachment 9111378 [details]
Bug 1599223 - remove target.bz2.complete.mar r=tomprince a=release

ESR Uplift Approval Request

• If this is not a sec:{high,crit} bug, please state case for ESR consideration: Unblock esr release
• User impact if declined: No esr release - mar signing will fail
• Fix Landed on Version: 72
• Risk to taking this patch: Low
• Why is the change risky/not risky? (and alternatives if risky): This will either unblock the release, or it will stay broken
• String or UUID changes made by this patch:

Comment 6

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/releases/mozilla-esr68/rev/64d9b4365269

Comment 7

[Aki Sasaki (not active)]

Attachment: Bug 1599223 - remove balrog toplevel bz2 submission. r=tomprince

Comment 8

[Aki Sasaki (not active)]

Looks like I missed the balrog toplevel bz2 portion in the esr68 patch, but not the m-c patch.

Comment 9

[Aki Sasaki (not active)]

Comment on attachment 9111437 [details]
Bug 1599223 - remove balrog toplevel bz2 submission. r=tomprince

ESR Uplift Approval Request

• If this is not a sec:{high,crit} bug, please state case for ESR consideration: Don't try to submit nonexistent bz2 toplevel entry
• User impact if declined: We may have broken update-verify testing and the like, not entirely sure.
• Fix Landed on Version: 72
• Risk to taking this patch: Low
• Why is the change risky/not risky? (and alternatives if risky):
• String or UUID changes made by this patch:

Comment 10

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/releases/mozilla-esr68/rev/fd17b62d5247

Comment 11

[Natalia Csoregi [:nataliaCs]]

https://hg.mozilla.org/mozilla-central/rev/9805fb607886

Comment 12

[Julien Cristau [:jcristau] (back April 22)]

Attachment: No bug - simplify package formats, esr is no longer different from other branches. r?#releng

We used to build extra bz2-compressed mar files for ESR, but that was
removed in bug 1599223.

Comment 13

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/9ec1cc2f8fea
No bug - simplify package formats, esr is no longer different from other branches. r=releng-reviewers,jmaher

Comment 14

[Noemi Erli[:noemi_erli]]

https://hg.mozilla.org/mozilla-central/rev/9ec1cc2f8fea