Foreman » Installer

Hi,

I just encountered a strange bug in foreman-installer. I try to install foreman on a rhel 7.2 server by following the official documentation available here :

https://www.theforeman.org/manuals/1.13/quickstart_guide.html

I have EPEL enabled on my server :

[2016-11-17 17:06:15 root@gvarhrepo1]# yum repolist
...
repo id repo name status
epel/x86_64 Extra Packages for Enterprise Linux 7 - x86_64 10,829
...

If I try to install maraidbserver it works well :

[2016-11-17 17:06:18 root@gvarhrepo1]# yum install mariadb-server
Loaded plugins: product-id, search-disabled-repos, subscription-manager
certificate verify failed
Resolving Dependencies
--> Running transaction check
---> Package mariadb-server.x86_64 1:5.5.52-1.el7 will be installed
--> Processing Dependency: mariadb(x86-64) = 1:5.5.52-1.el7 for package: 1:mariadb-server-5.5.52-1.el7.x86_64
etc...

My /etc/yum.repos.d/epel.repo :

[2016-11-17 17:08:47 root@gvarhrepo1]# cat /etc/yum.repos.d/epel.repo
[epel]
name=Extra Packages for Enterprise Linux 7 - $basearch
enabled=1
gpgcheck=1
gpgkey=https://fedoraproject.org/static/352C64E5.txt
#mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=$basearch
baseurl=http://download.fedoraproject.org/pub/epel/7/$basearch

when I run the command "foreman-installer", it fails because he change my /etc/yum.repos.d/epel.repo :

@[2016-11-17 17:08:50 root@gvarhrepo1]# foreman-installer
Execution of '/bin/yum -d 0 -e 0 -y install foreman-release-scl' returned 1: One of the configured repositories failed (Unknown),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

3. Disable the repository, so yum won't use it by default. Yum will then
        just ignore the repository until you permanently enable it again or use
        --enablerepo for temporary usage:

yum-config-manager --disable <repoid>

4. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again

@

My /etc/yum.repo.d/epel.repo after foreman-installer run :

[2016-11-17 17:10:18 root@gvarhrepo1]# cat /etc/yum.repos.d/epel.repo
[epel]
name=Extra Packages for Enterprise Linux 7 - $basearch
enabled=1
gpgcheck=1
gpgkey=https://fedoraproject.org/static/352C64E5.txt
#mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=$basearch
baseurl=http://download.fedoraproject.org/pub/epel/7/$basearch
mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=$basearch

There is baseurl and mirrorlist entries. This cause a crash in yum. If I try to install mariadb-server :

@[2016-11-17 17:11:05 root@gvarhrepo1]# yum install mariadb-server
Loaded plugins: product-id, search-disabled-repos, subscription-manager
certificate verify failed

One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

3. Disable the repository, so yum won't use it by default. Yum will then
        just ignore the repository until you permanently enable it again or use
        --enablerepo for temporary usage:

yum-config-manager --disable <repoid>

4. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
@
Foreman-installer don't have to change the configuration of my EPEL repo for run.