How to reproduce: 1. standard fedora33 cloud base image: ami-01efb339f953fdf36 2. install anything from the updates-modular repo (like perl-AutoLoader): sudo dnf -v install perl-AutoLoader
sudo dnf -v install perl-AutoLoader
When fetching metadata for the updates-modular repo:
Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3]
After dnf install command:
No available modular metadata for modular package 'perl-AutoLoader-5.74-471.module_f33+12592+71aff0e2.noarch', it cannot be installed on the system No available modular metadata for modular package 'perl-B-1.80-471.module_f33+12592+71aff0e2.x86_64', it cannot be installed on the system No available modular metadata for modular package 'perl-Carp-1.50-471.module_f33+12576+e1e4b70a.noarch', it cannot be installed on the system No available modular metadata for modular package 'perl-Class-Struct-0.66-471.module_f33+12592+71aff0e2.noarch', it cannot be installed on the system No available modular metadata for modular package 'perl-Data-Dumper-2.174-471.module_f33+12576+e1e4b70a.x86_64', it cannot be installed on the system No available modular metadata for modular package 'perl-Digest-1.20-1.module_f33+12831+24157273.noarch', it cannot be installed on the system
<img alt="full-logs.txt" src="/fedora-infrastructure/issue/raw/files/5e59f367ed4b6f7dce4d9607cedc9363de7d0e20eadf8da7f25ffa36e735ecfb-full-logs.txt" />
Metadata Update from @mohanboddu: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: medium-gain, medium-trouble, ops
Odd. I am unable to duplicate this.
Can you attach your /var/log/dnf.librepo.log ? Does a 'dnf clean all' change anything? What mirror are you using/getting?
Ah I should probably have mentioned the region too, sorry. I'm getting this in us-east-1.
us-east-1
Mirror I seem to be getting is http://mirror.arizona.edu/fedora/linux//updates/33/Modular/ for all of them.
http://mirror.arizona.edu/fedora/linux//updates/33/Modular/
<img alt="dnf.librepo.log" src="/fedora-infrastructure/issue/raw/files/6f8ebdc1493032a00c84e5e671b18c97f5f113bd48456c83dbc0c8356d014049-dnf.librepo.log" />
Dnf is crashing as well because metadata isn't present:
<img alt="dnf.log" src="/fedora-infrastructure/issue/raw/files/a7768edcd3661a59c7541b6c438ee8ca02bf54e93c08e5db91b7355a1295c6c5-dnf.log" />
Did some digging, and this is fixed by simply updating dnf/libmodulemd. ami-01efb339f953fdf36 isn't the official marketplace one, we should probably be using that.
Sorry for the noise.
Metadata Update from @gundersanne: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
The official market place one ( ami-0b416942dd362c53f ) has the same problem, but again dnf update fixes it. At most those images should probably be regenerated with newer dnf/libmodulemd?
We do actually make updated nightly images, but I don't know that we have any docs/pointers to them. You could check with the fedora cloud sig: https://fedoraproject.org/wiki/Cloud_SIG
Log in to comment on this ticket.