Bug 1710313 - Fedora 30 was released but registry.fedoraproject.org/fedora:latest is still Fedora 29
Summary: Fedora 30 was released but registry.fedoraproject.org/fedora:latest is still ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora Container Images
Classification: Fedora
Component: base
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Clement Verna
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-15 10:14 UTC by Jan Pazdziora (Red Hat)
Modified: 2019-07-07 08:22 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-07-07 08:22:38 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Jan Pazdziora (Red Hat) 2019-05-15 10:14:04 UTC 
Description of problem:

Fedora 30 was released but registry.fedoraproject.org/fedora:latest is still Fedora 29.

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

registry.fedoraproject.org/fedora:latest 81174df11aeb

How reproducible:

Deterministic.

Steps to Reproduce:
1. docker pull registry.fedoraproject.org/fedora:latest
2. docker run --rm registry.fedoraproject.org/fedora:latest cat /etc/fedora-release

Actual results:

Fedora release 29 (Twenty Nine)

Expected results:

Fedora release 30 (Thirty)

Additional info:
Comment 1 Clement Verna 2019-05-15 10:26:47 UTC 
Thanks for the report but we still did not have a working compose for Fedora 30 containers due to armhfp build failing this tracked in this ticket https://pagure.io/releng/issue/8173
Comment 2 Clement Verna 2019-07-07 08:22:38 UTC 
This is now fixed
Note You need to log in before you can comment on or make changes to this bug.