You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running yum/dnf commands such as dnf check-update I get the following errors:
[root@server ~]# dnf check-update
Updating Subscription Management repositories.
Extra Packages for Enterprise Linux Modular 8 - x86_64 41 kB/s | 93 kB 00:02
Errors during downloading metadata for repository 'epel-modular':
- Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=modular-epel8&arch=x86_64&infra=$infra&content=$contentdir (IP: 152.19.134.198)
- Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=modular-epel8&arch=x86_64&infra=$infra&content=$contentdir (IP: 85.236.55.6)
- Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=modular-epel8&arch=x86_64&infra=$infra&content=$contentdir (IP: 18.159.254.57)
Error: Failed to download metadata for repo 'epel-modular': Cannot prepare internal mirrorlist: Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=modular-epel8&arch=x86_64&infra=$infra&content=$contentdir (IP: 85.236.55.6)
When checking the URL manually with curl, I get the following error message:
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
I defined the following data in Hiera to install the built-in epel and epel-modular Repos for RHEL8:
This installs the repos defined at https://github.com/voxpupuli/puppet-yum/blob/v5.3.1/data/repos/RedHat/8.yaml
What are you seeing
When running yum/dnf commands such as
dnf check-updateI get the following errors:When checking the URL manually with curl, I get the following error message:
further down in the output, the valid repo-names are listed as:
What behaviour did you expect instead
I expect the repo 'epel-modular' to be installed with the correct URL, setting
repo=epel-modular-$releaseverand notrepo=modular-epel$releaseverOutput log
See above.
The text was updated successfully, but these errors were encountered: