Hello,
last week I required to provision some RHEL 6.8 VMs using Forman.
The last time this was the case some months ago.
We are using Foreman 1.12.0 on a RHEL 6 host.
During kick start install the following error was raised:
It took three days to find the issue on my local side.
I thought it has to do with our Proxy and DNS changes and Firewall
replacement.
I was replacing the local dvd media, changed the local web-server, analyzed
around with (No)SSL, switched for EPEL from mirrorlist to baseurl.
Played around with appending stage2… in PXE templates, tried to move EPEL
from Internet to my local Webserver.
And checked all logs I can found.
No success.
Then I found this:
So package puppet has been removed from EPEL 6 REPO!
Question is now to me: What is required to do to enable the - mandatory -
RHEL 6 Foreman provisioning again?
Which parts needs to be touched?
I did not find any post related to this in the mailing list.
Thanks for any help.
BR,
Anton
Auto Generated Inline Image 1 (11.6 KB)
Hi Anton,
Common repository (https://access.redhat.com/solutions/1184073) although
when I looked I did not find an ISO that contained RH Common. When I
searched the Red Hat Media iso's I located puppet packages on the Satellite
installation media. So on our kickstart server I include the Satellite
media iso and then in the kickstart configuration I add the Satellite repo
(e.g. repo --name="Satellite"
–baseurl=http://kickstart.example.com/kickstart/sat62_64 ). We currently
use a standalone kickstart server outside of Satellite but I imagine this
could also be done in Satellite provisioning. I believe there are
Satellite ISO's available for both rhel 6
(https://access.redhat.com/downloads/content/250/ver=6.2/rhel---6/6.2.7/x86_64/product-software)
and rhel 7
( https://access.redhat.com/downloads/content/250/ver=6.2/rhel---7/6.2.7/x86_64/product-software).
My intention is to kickstart and have puppet installed and once that is
done I would setup the hosts with the RH Common repository available
through satellite to keep the version of puppet in line with what Satellite
expects.
Not sure if that helps but I would also be interested in the answer to
your question or any comments on what I have done above to try and solve
this problem.
-Tomas
···
From my understanding the puppet packages for RHEL come from the RH
On Monday, February 27, 2017 at 3:08:08 AM UTC-5, antonm...@gmail.com wrote:
Hello,
last week I required to provision some RHEL 6.8 VMs using Forman.
The last time this was the case some months ago.
We are using Foreman 1.12.0 on a RHEL 6 host.
During kick start install the following error was raised:
It took three days to find the issue on my local side.
I thought it has to do with our Proxy and DNS changes and Firewall
replacement.
I was replacing the local dvd media, changed the local web-server,
analyzed around with (No)SSL, switched for EPEL from mirrorlist to baseurl.
Played around with appending stage2… in PXE templates, tried to move
EPEL from Internet to my local Webserver.
And checked all logs I can found.
No success.
Then I found this:
http://smoogespace.blogspot.fr/2016/11/where-has-puppet-gone-in-epel-6-and.html
http://smoogespace.blogspot.fr/2016/12/puppet-not-coming-back-to-epel-el-6.html
So package puppet has been removed from EPEL 6 REPO!
Question is now to me: What is required to do to enable the - mandatory -
RHEL 6 Foreman provisioning again?
Which parts needs to be touched?
I did not find any post related to this in the mailing list.
Thanks for any help.
BR,
Anton
> Then I found this:
> http://smoogespace.blogspot.fr/2016/11/where-has-puppet-gone-in-epel-6-and.html
> http://smoogespace.blogspot.fr/2016/12/puppet-not-coming-back-to-epel-el-6.html
>
> So package puppet has been removed from EPEL 6 REPO!
There are alternatives - Puppet publish two repositories, one containing
Puppet 3 and another containing Puppet 4
(https://docs.puppet.com/puppet/3.8/puppet_repositories.html,
https://docs.puppet.com/puppet/4.9/puppet_collections.html respectively.)
Or if you depend on provisioning servers with outdated software, you
should have a mirror of the repository and packages (use yum-utils'
reposync command). The packages are probably still in Fedora's Koji
instance.
> Question is now to me: What is required to do to enable the - mandatory
> - RHEL 6 Foreman provisioning again?
> Which parts needs to be touched?
Foreman's default templates accept two parameters to enable the Puppet
3.x or 4.x (PC1) repository during provisioning. Set them globally,
per-OS or per-host to "true" in Foreman:
enable-puppetlabs-repo - enables the 3.x repo
enable-puppetlabs-pc1-repo - enables the 4.x PC1 repo
···
On 25/02/17 12:36, antonmeier72@gmail.com wrote:
–
Dominic Cleal
dominic@cleal.org
