On try, docker images are set to expire in 1 year, but their artifacts expire in 1 month. This means that if you do changes to docker images on try, then come back a month later with the same changes, tasks that depend on those docker images will fail because they can't load the image anymore, as the cache points to the non-expired task that now has an expired artifact.

Before bug 1649987, all try tasks had their expiry capped at 28 days, but that specific code was removed.

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

:bxbrenden, since you are the author of the regressor, bug 1649987, could you take a look? Also, could you set the severity field?

For more information, please visit auto_nag documentation.

We hit this (or something very similar) with a level 3 release docker image, which I filed as https://bugzilla.mozilla.org/show_bug.cgi?id=1833507. Cross-referencing here in case the root cause is the same.

Set expiration-policy on docker-image tasks to make sure the image artifact
sticks around as long as the task, and avoid issues down the road when we try
to reuse a cached task only to fail when we can't download its artifact.

https://hg.mozilla.org/mozilla-central/rev/58e2722c8c99