Tomer, I hope this an appropriate place to make this comment.
It would be nice to see Foreman 2.1rc3 on CentOS 8 address the current incompatibility between Foreman 2.1rc{1,2} and EPEL on CentOS 8.{1,2}.
Problem: If you have installed Foreman on CentOS 8, you can not install EPEL without creating a versioning problem on dnf upgrade. This problem existed in Foreman 2.1rc1, but as the basic install does not require EPEL, I simply didn’t install epel-release on CentOS 8. The problem raises it head again if you try to install Ansible related functionality, as ansible is provided from the EPEL repository. I’ll summarize the problem here, as the referenced thread is very long.
The commands to reproduce the problem on a CentOS 8 system with Foreman 2.1rc{1,2} installed:
sudo yum -y upgrade # Nothing to do
sudo yum -y install epel-release
sudo yum -y upgrade # Problem see below
sudo yum -y erase epel-release
sudo yum -y upgrade # Nothing to do
Just the error generated for brevity:
Error:
Problem: package foreman-2.1.0-0.20.rc2.el8.noarch requires rubygem(net-ssh) = 4.2.0, but none of the providers can be installed
- cannot install both rubygem-net-ssh-5.1.0-2.el8.noarch and rubygem-net-ssh-4.2.0-2.el8.noarch
- cannot install both rubygem-net-ssh-4.2.0-2.el8.noarch and rubygem-net-ssh-5.1.0-2.el8.noarch
- cannot install the best update candidate for package rubygem-net-ssh-4.2.0-2.el8.noarch
- cannot install the best update candidate for package foreman-2.1.0-0.20.rc2.el8.noarch
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
PS: The reference to the longer running thread: