Skip to content

config forking should ensure image tag is valid #34675

Open
@BenTheElder

Description

@BenTheElder

What happened:

#34651 (comment) / #34672

because we introduced the 1.33 image variants a few days ago, but haven't bumped the jobs to new images, the mutated image tag from the existing jobs to -1.33 was not available, causing jobs to fail

What you expected to happen:

We should probably detect and handle this. It might make sense to just adopt the latest available on the new branch.

How to reproduce it (as minimally and precisely as possible):
n/a

Please provide links to example occurrences, if any:

n/a

Anything else we need to know?:

Low prio, something to consider before ~4 months from now.

/sig release testing

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.sig/releaseCategorizes an issue or PR as relevant to SIG Release.sig/testingCategorizes an issue or PR as relevant to SIG Testing.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions