Bug 2151833

Summary:	no matching manifest for linux/amd64 in the manifest list entries
Product:	[Fedora] Fedora Container Images	Reporter:	Jan Pazdziora (Red Hat) <jpazdziora>
Component:	base	Assignee:	Clement Verna <clems.verna>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	adrian, carlos.sepulveda, jaruga, jpazdziora, kevin
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:	2022-12-08 20:56:24 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) 2022-12-08 09:20:47 UTC

Description of problem:

The registry.fedoraproject.org/fedora:rawhide seems broken.

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

registry.fedoraproject.org/fedora:rawhide as of today.

How reproducible:

Deterministic.

Steps to Reproduce:
1. docker pull registry.fedoraproject.org/fedora:rawhide
2. podman pull registry.fedoraproject.org/fedora:rawhide
3.

Actual results:

$ docker pull registry.fedoraproject.org/fedora:rawhide
rawhide: Pulling from fedora
no matching manifest for linux/amd64 in the manifest list entries

$ podman pull registry.fedoraproject.org/fedora:rawhide
Trying to pull registry.fedoraproject.org/fedora:rawhide...
Error: choosing an image from manifest list docker://registry.fedoraproject.org/fedora:rawhide: no image found in manifest list for architecture amd64, variant "", OS linux

Expected results:

No error, image pulls fine.

Additional info:

This is on x86_64 Fedora 37 but also observed in GitHub Actions setups (Ubuntu x86_64 22.04).

Comment 1 Clement Verna 2022-12-08 10:01:41 UTC

Yes our images build are broken except for rawhide aarch64 that seems to work from time to time.

Need to spend some time investigating the root cause of the build failures.

More details here https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/FSCCXXQKCLKO2LUO5E72QE6XQKNDUYN7/

Comment 2 Jan Pazdziora (Red Hat) 2022-12-08 12:16:21 UTC

Thanks for the quick info.

Would it make sense to only push new images when builds on all architectures passed? IOW, decouple any build issues from availability of use of existing, already published images.

Comment 3 Clement Verna 2022-12-08 12:21:35 UTC

This is the case for all the releases except rawhide, where it is expected for builds to be failing more regularly.

Comment 4 Clement Verna 2022-12-08 20:56:24 UTC

This is now fixed 

[cverna@localhost]  $ podman pull registry.fedoraproject.org/fedora:rawhide
Trying to pull registry.fedoraproject.org/fedora:rawhide...
Getting image source signatures
Copying blob 5e41d495e700 done  
Copying config 3277db395a done  
Writing manifest to image destination
Storing signatures
3277db395a47825d096612f824a06ee95c5d4b7334d3f8b09eac76c1072f8707

Comment 5 Adrian Reber 2022-12-09 14:44:34 UTC

I still see errors with this container image:

$ podman pull registry.fedoraproject.org/fedora:rawhide
Trying to pull registry.fedoraproject.org/fedora:rawhide...
Error: choosing an image from manifest list docker://registry.fedoraproject.org/fedora:rawhide: no image found in manifest list for architecture amd64, variant "", OS linux

Comment 6 Clement Verna 2022-12-09 15:10:43 UTC

Hum indeed, this should be fixed now. Our upload script needed a small fix --> https://pagure.io/releng/pull-request/11179#

Comment 7 Adrian Reber 2022-12-09 15:14:55 UTC

It is fixed now for me. Thanks.