build_suggestions: bump 4.21 minimum upgrade version to 4.20.12

[haircommander]

so upgrades go through openshift/machine-config-operator#5516

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[haircommander]

context: in cri-o 1.33, a change cri-o/cri-o#8962 was made to the default limits set for CRI-O. Now, the ulimit nofile is set much lower, with space to set it higher. however, some workloads don't expect this change, and fail (see https://issues.redhat.com/browse/OCPBUGS-62095)

This was worked around temporarily in openshift/machine-config-operator#5308, but that workaround was not intendd to be carried in to 4.21.

Instead, we should drop-in an ignition file on upgrades from 4.20 to 4.21 to make sure existing clusters don't get this change, but new clusters started in 4.21 do.

Now we need to make sure upgrades go through that PR. it missed 4.20.11 by a day, so I feel confident it will land in 4.20.12

[wking]

Does look like OCPBUGS-70201 missed 4.20.11. So we expect it to be in 4.20.12. But let's wait until 4.20.12 exists, so we can confirm for sure, because sometimes ART picks special things as the source of a release image.

[haircommander]

works for me, as long as we can get something like this in for upgrades to 4.21.0

/hold

[wking]

OCPBUGS-70201 is confirmed present in https://amd64.ocp.releases.ci.openshift.org/releasestream/4-stable/release/4.20.12 .

/hold cancel

[wking]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: haircommander, wking

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• build-suggestions/OWNERS [wking]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@haircommander: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.