Bug 1710313

Summary:	Fedora 30 was released but registry.fedoraproject.org/fedora:latest is still Fedora 29
Product:	[Fedora] Fedora Container Images	Reporter:	Jan Pazdziora (Red Hat) <jpazdziora>
Component:	base	Assignee:	Clement Verna <clems.verna>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	29
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-07-07 08:22:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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