Hi,
I set my system up to us the epel, puppet & foreman repos.
I do a yum install puppet and it installs ok including some updates etc.
from epel.
So why do I get:
/Stage[main]/Tftp::Install/Package[syslinux]/ensure: change from absent to
present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install syslinux'
returned 1: Error: Cannot retrieve metalink for repository: epel. Please
verify its path and try again
When I run the Foreman installer?
Also for some of my work I will be on a isolated network no internet
connection so I will need to build my own repos.
Therefore I need to be able to install Foreman without it changing my repos.
I can handle missing packages no problem.
Regards, Mike.
Pass --foreman-configure-epel-repo=false.
···
On 19/03/14 12:27, Michael Hurn wrote:
>
> Hi,
>
> I set my system up to us the epel, puppet & foreman repos.
>
> I do a yum install puppet and it installs ok including some updates etc.
> from epel.
>
> So why do I get:
> /Stage[main]/Tftp::Install/Package[syslinux]/ensure: change from absent
> to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install
> syslinux' returned 1: Error: Cannot retrieve metalink for repository:
> epel. Please verify its path and try again
>
> When I run the Foreman installer?
>
> Also for some of my work I will be on a isolated network no internet
> connection so I will need to build my own repos.
>
> Therefore I need to be able to install Foreman without it changing my repos.
> I can handle missing packages no problem.
–
Dominic Cleal
Red Hat Engineering
Are you using a proxy/cacher? I''ve had issues with package cacher's
not being happy with mirrorlist directives and I've switched to using
a direct baseurl in the epel.repo file. The Foreman-Installer will by
default reinstate the mirrorlist directive, but you can stop that by
setting "configure_epel_repo: false" in the installer - however, be
sure your EPEL repo is definitely working if you do 
Greg
···
On 19 March 2014 12:27, Michael Hurn wrote:
>
> Hi,
>
> I set my system up to us the epel, puppet & foreman repos.
>
> I do a yum install puppet and it installs ok including some updates etc.
> from epel.
>
> So why do I get:
> /Stage[main]/Tftp::Install/Package[syslinux]/ensure: change from absent to
> present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install syslinux'
> returned 1: Error: Cannot retrieve metalink for repository: epel. Please
> verify its path and try again
Thank you Greg & Dominic for the response.
Can you please give a list for the other repos?
I have found:
foreman-custom-repo
foreman-proxy-repo
foreman-proxy-custom-repo
Do I need to set all of them to false?
···
On Wed, Mar 19, 2014 at 9:00 AM, Dominic Cleal wrote:
On 19/03/14 12:27, Michael Hurn wrote:
Hi,
I set my system up to us the epel, puppet & foreman repos.
I do a yum install puppet and it installs ok including some updates etc.
from epel.
So why do I get:
/Stage[main]/Tftp::Install/Package[syslinux]/ensure: change from absent
to present failed: Execution of ‘/usr/bin/yum -d 0 -e 0 -y install
syslinux’ returned 1: Error: Cannot retrieve metalink for repository:
epel. Please verify its path and try again
When I run the Foreman installer?
Also for some of my work I will be on a isolated network no internet
connection so I will need to build my own repos.
Therefore I need to be able to install Foreman without it changing my
repos.
I can handle missing packages no problem.
Pass --foreman-configure-epel-repo=false.
–
Dominic Cleal
Red Hat Engineering
–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/C7WnNHE0S3U/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
> Thank you Greg & Dominic for the response.
> Can you please give a list for the other repos?
> I have found:
> foreman-custom-repo
This one stops the "foreman" repo(s) being managed, we usually set it to
true by default in the foreman-installer packages as the assumption is
you're using foreman-release.rpm instead.
> foreman-proxy-repo
This is the name of the repo to use if custom-repo is false, e.g. the
release version.
> foreman-proxy-custom-repo
Same as foreman-custom-repo but for the proxy, again, should be enabled
by default to prevent management.
So assuming those are still enabled like the defaults, the other one is
–foreman-configure-scl-repo which manages the Software Collections repo
on EL6 clones (not RHEL). This can be set to false to disable it.
···
On 19/03/14 13:26, Michael Hurn wrote:
–
Dominic Cleal
Red Hat Engineering
Thank you I was also missing the SCL repo.
BTW is there a setting for the Puppet repos?
At the office I have more proxies to deal with so I may not be able to test
until this evening. (I am in Ottawa, Eastern time.)
···
On Wed, Mar 19, 2014 at 9:37 AM, Dominic Cleal wrote:
On 19/03/14 13:26, Michael Hurn wrote:
Thank you Greg & Dominic for the response.
Can you please give a list for the other repos?
I have found:
foreman-custom-repo
This one stops the “foreman” repo(s) being managed, we usually set it to
true by default in the foreman-installer packages as the assumption is
you’re using foreman-release.rpm instead.
foreman-proxy-repo
This is the name of the repo to use if custom-repo is false, e.g. the
release version.
foreman-proxy-custom-repo
Same as foreman-custom-repo but for the proxy, again, should be enabled
by default to prevent management.
So assuming those are still enabled like the defaults, the other one is
–foreman-configure-scl-repo which manages the Software Collections repo
on EL6 clones (not RHEL). This can be set to false to disable it.
–
Dominic Cleal
Red Hat Engineering
–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/C7WnNHE0S3U/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
There isn't, it's up to you to configure the Puppet Labs repo if you
want it, else it will probably pull Puppet from EPEL instead.
···
On 19/03/14 13:56, Michael Hurn wrote:
> Thank you I was also missing the SCL repo.
> BTW is there a setting for the Puppet repos?
> At the office I have more proxies to deal with so I may not be able to
> test until this evening. (I am in Ottawa, Eastern time.)
–
Dominic Cleal
Red Hat Engineering
