On Mon, 8 May 2023 at 15:58, Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx> wrote:
On Mon, May 08, 2023 at 09:24:08AM -0700, Kevin Fenzi wrote:
> I'd like to note that making this blocking doesn't waive any kind of
> magic wand that makes our infrastructure more reliable. ;)
> The container build pipeline is a long collection of fragile things.
> It may well result in us slipping more based on things not working. ;(
Hmm, quoting from https://pagure.io/releng/issue/11092:
>> Also the aarch64 cluster is running on Fedora 33 boxes, so we
>> should probably try to do a full redeploy :-(
> We can't upgrade it from f33 because docker is no longer in f34+ and
> openshift origin / 3.11 doesn't support any newer either.
Is this still true? I don't think we want to make the Fedora release
process contingent on something that requires F33.
```
$ sudo -i ssh osbs-aarch64-node01.iad2.fedoraproject.org cat /etc/system-release
Fedora release 33 (Thirty Three)```
My memory of this is that this is not an easy thing to 'fix'.
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
