fedora-infrastructure

#12386 GNOME Software upgrade to Fedora 42 is broken
Closed: Fixed by kevin. Opened by catanzaro.

Closed: Fixed
Reopen Issue

Describe what you would like us to do:

As of today, GNOME Software allows upgrading to Fedora 42 when the show-upgrades-prerelease setting is enabled. Presumably somebody pushed some sort of metadata to expose the upgrade. However, it is broken:

15:10:35:737 Gs  non-interactive action 'unknown' failed with error 'download-failed': cannot update repo 'fedora': Cannot prepare internal mirrorlist: Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=fedora-42&arch=x86_64 (IP: 2600:1f14:fad:5c02:7c8a:72d0:1c58:c189); Last error: Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=fedora-42&arch=x86_64 (IP: 2600:1f14:fad:5c02:7c8a:72d0:1c58:c189)
15:10:35:737 Gs  not handling non-interactive error 'download-failed' for action 'unknown': cannot update repo 'fedora': Cannot prepare internal mirrorlist: Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=fedora-42&arch=x86_64 (IP: 2600:1f14:fad:5c02:7c8a:72d0:1c58:c189); Last error: Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=fedora-42&arch=x86_64 (IP: 2600:1f14:fad:5c02:7c8a:72d0:1c58:c189)

We should either fix the 404 or else pull the upgrade to Fedora 42 until it's ready.

When do you need this to be done by? (YYYY/MM/DD)

Preferably 2025/02/05

That is probably more ticket for https://pagure.io/releng/issues/, but from I know there isn't any F42 compose yet, so it's expected to fail now.
Edited by zlopez

Metadata Update from @zlopez:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

Please don't close this ticket until the upgrade is pulled. Releasing an upgrade and then saying it's expected to fail is not OK.

Metadata Update from @catanzaro:
- Issue status updated to: Open (was: Closed)

Yes, it was intended that this would work when or soon after the change was made... but there were issues.

First the compose didn't finish fully, got that fixed and then it didn't sync right, and finally we thought it was synced and done but there was a metadata issue that prevented the link from becoming live in mirrormanager.

Anyhow, it's fixed now.

@jnsamyak another item for your retrospective? Perhaps we could wait to push this until after we are 100% sure it's ready?

But also, this is the vastly small number of people who opt into under development releases and also go and try and upgrade to them. I dont think this is very many people?

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Thanks.

But also, this is the vastly small number of people who opt into under development releases and also go and try and upgrade to them. I dont think this is very many people?

It shouldn't be too many people, yes.

Every 6 months users do complain on reddit that the update is available early, why is Fedora allowing me to update so early? I think these users are just manually changing the value of the preference and just forgetting that they've done so.

Please don't close this ticket until the upgrade is pulled. Releasing an upgrade and then saying it's expected to fail is not OK.

I didn't close it because it wasn't fixed, I closed it because it should be reopen on releng tracker. But as it is already fixed it doesn't matter anymore.
Metadata
None
None
None
None
Lowest
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.