Bug 2276864 - registry.fedoraproject.org/fedora:latest points to Fedora 39
Summary: registry.fedoraproject.org/fedora:latest points to Fedora 39
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora Container Images
Classification: Fedora
Component: base
Version: 40
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Clement Verna
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-04-24 11:28 UTC by Benjamin Gilbert
Modified: 2024-04-24 18:48 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-04-24 15:05:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Benjamin Gilbert 2024-04-24 11:28:35 UTC
Description of problem:
Fedora 40 has been released but registry.fedoraproject.org/fedora:latest is still Fedora 39.

Version-Release number of selected component (if applicable):
n/a

How reproducible:
Always

Steps to Reproduce:
1. podman run --pull=always -ti --rm registry.fedoraproject.org/fedora:latest cat /etc/fedora-release

Actual results:
Fedora release 39 (Thirty Nine)


Expected results:
Fedora release 40 (Forty)


Additional info:
This appears to be a recurring issue after a Fedora release (bug 1654943, bug 1710313, bug 2065870, bug 2090439, https://pagure.io/ContainerSIG/container-sig/issue/59).  Is there a process or checklist change that could help ensure the label is updated during release?

Comment 1 Clement Verna 2024-04-24 15:02:52 UTC
Working on it.

Comment 2 Clement Verna 2024-04-24 15:04:53 UTC
Merged https://pagure.io/releng/pull-request/12079 and ran the release script.

podman run --pull=always -ti --rm registry.fedoraproject.org/fedora:latest cat /etc/fedora-release
Trying to pull registry.fedoraproject.org/fedora:latest...
Getting image source signatures
Copying blob 0091ef30bf40 done   | 
Copying config 2ecd175602 done   | 
Writing manifest to image destination
Fedora release 40 (Forty)

Comment 3 Clement Verna 2024-04-24 15:05:27 UTC
Thanks for the report Benjamin, I hope you are doing well :-)

Comment 4 Benjamin Gilbert 2024-04-24 15:34:58 UTC
Thanks Clement!  Is there something that can be done to better integrate this step into the Fedora release process?

Comment 5 Clement Verna 2024-04-24 18:48:38 UTC
Opened a PR to document the steps needed to be done by the releng team --> https://pagure.io/infra-docs-fpo/pull-request/286#


Note You need to log in before you can comment on or make changes to this bug.