Closed Bug 1599223 Opened 10 months ago Closed 10 months ago

remove target.bz2.complete.mar from esr68

Categories

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

task
Not set
normal

Tracking

(firefox-esr68 fixed, firefox72 fixed)

RESOLVED FIXED
Tracking Status
firefox-esr68 --- fixed
firefox72 --- fixed

People

(Reporter: aki, Assigned: aki)

References

Details

Attachments

(3 files)

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.

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.

Pushed by asasaki@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/9805fb607886
remove target.bz2.complete.mar r=tomprince

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:
Attachment #9111378 - Flags: approval-mozilla-esr68?
Attachment #9111378 - Flags: approval-mozilla-esr68? → approval-mozilla-esr68+

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

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:
Attachment #9111437 - Flags: approval-mozilla-esr68?
Attachment #9111437 - Flags: approval-mozilla-esr68? → approval-mozilla-esr68+
Status: NEW → RESOLVED
Closed: 10 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.