1933405 - beetmover-repackage CoT failures due to relative-timestamp expiry

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P1)

Description

[Julien Cristau [:jcristau]]

Attachment: chain_of_trust.log

The 134.0b1 promote graph failed, with CoT errors related to the "expiry" fields in the task payloads.

Comment 1

[Julien Cristau [:jcristau]]

I guess there's a couple of ways to fix this:

• teach CoT about relative-datestamp, add code to translate it to actual timestamps before comparison (possibly via a dependency on taskgraph? ick.)
• add the expiry field to the ignored fields in CoT verification; probably easier, but I'm not super happy about it because it's so specific to beetmover.

Comment 2

[BMO Github Automation]

Attachment: [mozilla-releng/scriptworker] Bug 1933405 - resolve relative-datestamp in CoT verification (#673)

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1932190

Comment 4

[Julien Cristau [:jcristau]]

The fix is part of scriptworker 60.5.0 (https://pypi.org/project/scriptworker/60.5.0/). The next scheduled deployment that would pick it up is next Tuesday (December 3rd), presumably that's good enough from the 135 pov?

Comment 5

[Donal Meehan [:dmeehan]]

(In reply to Julien Cristau [:jcristau] from comment #4)

The fix is part of scriptworker 60.5.0 (https://pypi.org/project/scriptworker/60.5.0/). The next scheduled deployment that would pick it up is next Tuesday (December 3rd), presumably that's good enough from the 135 pov?

Perfect, aiui this won't impact 135 until merge day 2025-01-06

Comment 6

[Julien Cristau [:jcristau]]

Deployed yesterday, verified in a staging release:
https://treeherder.mozilla.org/jobs?repo=try&revision=bf916cb429142eba4fc8e1ebd1c03516276bd504