Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Hi there and thank you for reading,

I am currently in the process of setting up a puppet service for our ec2 instances and decided to give foreman a try (node certificate management and automatic passenger setup seems nice).

Unfortunately I'm running into difficulties with the installation. I'm on fresh a 'Amazon Linux AMI x86_64 PV':

[root@hostname ~]# uname -a
Linux hostname 3.10.35-43.137.amzn1.x86_64 #1 SMP Wed Apr 2 09:36:59 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

and tried the following:

sudo yum -y update
sudo yum -y install http://yum.theforeman.org/releases/1.1/el6/x86_64/foreman-release.rpm
sudo yum -y install foreman-installer

which results in this:

Error: Package: rubygem-foreman_api-0.1.11-1.el6.noarch (foreman)
       Requires: rubygem(rest-client) >= 1.6.1
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

The suggestions seem useless (--skip-broken installs all dependencies but foreman/puppet). I ended up here and tried installing the repository (after removing the old one)

sudo yum -y remove epel-release
sudo yum -y install http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm

now again, what I tried:

sudo -y update
sudo -y install foreman-installer

results in the same error. Installation without previous update is possible (though yum will complain about Public keys) and results in the following error:

[ec2-user@hostname ~]$ foreman-installer
/usr/share/ruby/vendor_ruby/2.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- highline/import (LoadError)
        from /usr/share/ruby/vendor_ruby/2.0/rubygems/core_ext/kernel_require.rb:55:in `require'
        from /usr/sbin/foreman-installer:3:in `<main>'

I had similar problems while trying to set up passenger and eventually surrendered. I assume this happens due to conflicting ruby version, so:

[root@hostname puppet]# ruby --version
ruby 2.0.0p451 (2014-02-24 revision 45167) [x86_64-linux]
[root@hostname puppet]# gem --version
[root@hostname puppet]# ls /usr/bin | grep ruby
[root@hostname puppet]# ls /usr/bin | grep gem

Did someone run into the same issues? How do I resolve this?

Thanks in advance and thank you for reading through all this!

share|improve this question
I ran into this same problem - I refuse to believe that there is 'no' solution, there must be a a way, I'll have to ask the foreman guys if they have a solution –  Mister IT Guru Jul 16 at 15:24

2 Answers 2

up vote 1 down vote accepted

Packages for Red Hat Enterprise Linux and its clones are not compatible with Amazon Linux. You will need to find either a different way to install Foreman, or preferably a different Linux distribution (Amazon Linux has many issues which make it generally unsuitable for just about anything).

share|improve this answer
Wow alright, I never even thought of that.. at least I know what to look for in the future. I think I'll cry a little now. Thanks for the impossibly fast answer! –  afriemann Jun 12 at 16:47

I had the same error on a CentOS 6 system. It turns out that I needed to install an additional repository as described in the installation guide for the foreman:


All RHEL and derivatives require Red Hat Software Collections (RHSCL) 1.0 or rebuild, e.g. Software Collections for CentOS. RHSCL is available to RHEL customers as a separate repository or child channel. More information on Software Collections for CentOS is available here and for Scientific Linux it is available here.

I assume your should do something similar in your AWS instance.

share|improve this answer
Unfortunately that did not help (I already tried that prior to asking my question). As Michael suggested, the Amazon Linux distribution seems incompatible. We switched to a RHEL AMI and got it working eventually (even though we trashed foreman and simply went for passenger+puppet, which works like a charm). Thanks anyway! –  afriemann Jun 26 at 17:02

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.