scenario: I inherited the admin of a foreman installation, with stuff all documentation from its previous admin. I’m learning on my feet, slowly, as i go along so if anything that follows seems daft, or Foreman 101, that’s why.
Ive done a bit more reading and background and have ended up trying to just install on a nice fresh vanilla rhel8 build unregistered to redhat.
Updating Subscription Management repositories.
Puppet 7 Repository el 9 - x86_64 0.0 B/s | 0 B 00:00
Errors during downloading metadata for repository ‘puppet7’:
Curl error (56): Failure when receiving data from the peer for http://yum.puppet.com/puppet7/el/9/x86_64/repodata/repomd.xml [Recv failure: Connection reset by peer]
Error: Failed to download metadata for repo ‘puppet7’: Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
Expected outcome:
successful completion of foreman installation as per those foreman install directions etc
Foreman and Proxy versions:
foreman-release-3.4.1-1.el8.noarch
Foreman and Proxy plugin versions:
Dont know how to ascertain that
Distribution and version:
Dont know how to ascertain that
Other relevant data:
N/A
all and any help, pointers, advice gratefully received, but merely saying “go away and read about it” doesnt solve my predicament ie the official install instructions don’t work.
Are you sure you’re reading the correct documentation for Foreman version 3.4? The dnf module command you posted refers to the “el9” as in RHEL 9 which is required from Foreman version 3.12, I believe? The document you linked that you followed doesn’t have the el9 mentioned anywhere. Please, double check that you’re on the correct version of the documentation in the top right corner of the page.
Good luck!
Note: Maybe you should consider upgrading to the latest supported version of Foreman with Katello. You can only upgrade one minor version at a time. No jumping over any of them or you can face major issues and broken installation. Pay attention to the jump from RHEL 8 to RHEL 9 at version 3.12. There is in-place upgrade guide available too.
Are you using a proxy in between the Foreman install and the Puppet repo that could be causing an issue with SSL or a caching issue? Is the time correct on the system as well?
If you try to manually make the Puppet repo with the following contents in /etc/yum.repos.d/puppet. Repo
Total size: 9.3 k Installed size: 3.3 k Downloading Packages: Running transaction check Invalid tsflag in config file: repackage Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction
Updating Subscription Management repositories. Unable to read consumer identity
This system is not registered with an entitlement server. You can use “rhc” or “subscription-manager” to register.
Puppet 8 Repository el 9 - x86_64 0.0 B/s | 0 B 00:00 Errors during downloading metadata for repository ‘puppet8’:
Curl error (56): Failure when receiving data from the peer for http://yum.puppet.com/puppet8/el/9/x86_64/repodata/repomd.xml [Recv failure: Connection reset by peer]* Error: Failed to download metadata for repo ‘puppet8’: Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
This system is not registered with an entitlement server. You can use “rhc” or “subscription-manager” to register.
DNF version: 4.14.0 cachedir: /var/cache/dnf Extra Packages for Enterprise Linux 9 - x86_64 17 MB/s | 20 MB 00:01 Extra Packages for Enterprise Linux 9 openh264 (From Cisco) - x86_64 2.2 kB/s | 2.5 kB 00:01 Puppet 8 Repository el 9 - x86_64 0.0 B/s | 0 B 00:00 Errors during downloading metadata for repository ‘puppet8’:
Curl error (56): Failure when receiving data from the peer for http://yum.puppet.com/puppet8/el/9/x86_64/repodata/repomd.xml [Recv failure: Connection reset by peer]* Error: Failed to download metadata for repo ‘puppet8’: Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0* Trying 18.244.164.90:80…
Connected to yum.puppet.com (18.244.164.90) port 80 (#0)
GET /puppet8/el/9/x86_64/repodata/repomd.xml HTTP/1.1
Host: yum.puppet.com
User-Agent: curl/7.76.1
Accept: /
That’s really odd. The only thing I can think of would be a firewall which inspects the traffic and doesn’t like it. As dnf uses different headers then curl that may explain the difference.
You could try to set the repo to https, i.e. change the line
and… gvde is bang on. various tests did indeed eventually show that networks hadn’t opened port 80 despite being asked to and confirming they had some while ago.
Thanks all for you help - this thread is now closed.
Though I may be opening another as now I’ve managed to run