#9184 Flatpak build: Unable to fetch manifest list or v2 schema 2 digest for registry.fedoraproject.org/flatpak-build-base:latest
Closed: Duplicate 3 years ago by smooge. Opened 3 years ago by mcrha.

I just issues fedpkg flatpak-build, which resulted in https://koji.fedoraproject.org/koji/taskinfo?taskID=48250551 and it failed with Unable to fetch manifest list or v2 schema 2 digest for registry.fedoraproject.org/flatpak-build-base:latest. Looking into the log, I also notice there these warnings:

2020-07-31 09:24:49,386 platform:- - atomic_reactor.plugins.check_and_set_platforms - INFO - Checking koji target for platforms
2020-07-31 09:24:49,461 platform:- - atomic_reactor.plugins.check_and_set_platforms - INFO - Koji platforms are ['aarch64', 'armv7hl', 'i686', 'ppc64le', 's390x', 'x86_64']
2020-07-31 09:24:49,461 platform:- - atomic_reactor.plugins.check_and_set_platforms - WARNING - No cluster found for platform 'armv7hl' in reactor config map, skipping
2020-07-31 09:24:49,461 platform:- - atomic_reactor.plugins.check_and_set_platforms - WARNING - No cluster found for platform 'i686' in reactor config map, skipping
2020-07-31 09:24:49,461 platform:- - atomic_reactor.plugins.check_and_set_platforms - WARNING - No cluster found for platform 'aarch64' in reactor config map, skipping
2020-07-31 09:24:49,461 platform:- - atomic_reactor.plugins.check_and_set_platforms - WARNING - No cluster found for platform 'ppc64le' in reactor config map, skipping
2020-07-31 09:24:49,461 platform:- - atomic_reactor.plugins.check_and_set_platforms - WARNING - No cluster found for platform 's390x' in reactor config map, skipping

but I've no idea whether they are related or not.


I would suspect a transient problem with the registry. My flatpak builds both before and after yours worked just fine.

This seems to be related to 9175. Could you resubmit and see if it fixes the problem. If not we will track it in 9175

Metadata Update from @smooge:
- Issue close_status updated to: Duplicate
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue status updated to: Closed (was: Open)
- Issue tagged with: groomed, medium-gain, medium-trouble

3 years ago

Login to comment on this ticket.

Metadata