Trouble with versions when installing

Hi,

I am new to foreman and puppet - I'm installing both for the first time (on
RHEL6). Consequently my options are pretty much open when it comes to
installing and re-installing. I'm installing on a fresh VM and can easily
revert to a snapshot before the Foreman install was started.

The problem I've hit is that although I can successfully install Foreman
1.5 it brings in Puppet 2.7.25. Then when I install puppet agent on my
existing nodes it is coming down as version 3.6.1. I didn't realise that
was a problem initially, but I soon hit problems which when google revealed
that the client version should not exceed the server version.

So, the big question is which is the latest stable version of puppet that I
can use with Foreman 1.5?

The next question (assuming the answer to the previous question is >
2.7.25) is why is it not brought in automatically by the Foreman installer?

Finally, what are my options from the point? Ideally I would like to
re-run my Foreman installation and force it to bring in a later version of
Puppet. Next best would be to upgrade puppet post install. Least good
would be to install an older version of the client.

Thanks in advance for any assistance.

David

PS, Here is the process I'm using to install Foreman:

yum -y install
http://yum.theforeman.org/releases/1.5/el6/x86_64/foreman-release.rpm
wget
http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
rpm -ivh epel-release-6-8.noarch.rpm
yum -y install foreman-installer
foreman-installer -i --enable-foreman --enable-foreman-compute-ec2
–enable-foreman-compute-gce --enable-foreman-compute-libvirt
–enable-foreman-compute-openstack --enable-foreman-compute-ovirt
–enable-foreman-compute-rackspace --enable-foreman-compute-vmware
–no-enable-foreman-plugin-bootdisk --no-enable-foreman-plugin-chef
–enable-foreman-plugin-default-hostgroup
–enable-foreman-plugin-discovery --enable-foreman-plugin-hooks
–enable-foreman-plugin-puppetdb --enable-foreman-plugin-setup
–enable-foreman-plugin-templates --enable-foreman-proxy --enable-puppet
–foreman-db-username='foreman' --foreman-db-password='dbaRgr8'
–foreman-unattended='true' --puppet-agent='true'
–puppet-runmode='service' --puppet-server='true'
–puppet-server-facts='true'
–foreman-foreman-url='https://foreman.bluecrest.local/'

On the client I am doing this to install puppet:

rpm -ivh http://yum.puppetlabs.com/puppetlabs-release-el-6.noarch.rpm
yum install puppet

> So, the big question is which is the latest stable version of puppet that I
> can use with Foreman 1.5?

Hello,

we do support most of Puppet versions. There are some exceptions:

http://theforeman.org/manuals/1.5/#3.1.2PuppetCompatibility

What is the usual process is to install Foreman which pulls Puppet from
EPEL. Then you can upgrade Puppet to any other version you want (e.g.
Puppet Labs repo). Or you can do this even before the installation, our
installer is compatible with most versions - see the table above.

··· -- Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman

Hi,

Thanks for that.

I have subsequently realised that I was using a mix of epel and puppet lab
repositories and that was the source of my problem. Sorry for the time
waste! I have Foreman, Puppet and a smart-proxy all working now. :slight_smile:

David

··· On Friday, 6 June 2014 08:20:05 UTC+1, Lukas Zapletal wrote: > > > So, the big question is which is the latest stable version of puppet > that I > > can use with Foreman 1.5? > > Hello, > > we do support most of Puppet versions. There are some exceptions: > > http://theforeman.org/manuals/1.5/#3.1.2PuppetCompatibility > > What is the usual process is to install Foreman which pulls Puppet from > EPEL. Then you can upgrade Puppet to any other version you want (e.g. > Puppet Labs repo). Or you can do this even before the installation, our > installer is compatible with most versions - see the table above. > > -- > Later, > > Lukas "lzap" Zapletal > irc: lzap #theforeman >

Just a helpful tip…The yum versionlock plugin is really nice for locking
in the puppet/puppetmaster version on your foreman server while still using
the puppetlabs repo. I've been running Puppet on a 3.x version with
Foreman since 1.2 or so. I have run into a few puppet version issues along
the way. But they become much less of an issue with the versionlock plugin
and the ease of being about do a yum downgrade.

Also, we deploy puppet agents out of EPEL almost everywhere, they roll
along just fine not caring about the version of puppet on the
master/foreman server.

Sean M. Alderman
Senior Engineer, UDit Systems Integration and Engineering
University of Dayton
salderman1@udayton.edu

"We are not some casual and meaningless product of evolution. Each of us
is the result of a thought of God. Each of us is willed. Each of us is
loved. Each of us is necessary."
- BXVI

··· On Fri, Jun 6, 2014 at 6:53 AM, wrote:

Hi,

Thanks for that.

I have subsequently realised that I was using a mix of epel and puppet lab
repositories and that was the source of my problem. Sorry for the time
waste! I have Foreman, Puppet and a smart-proxy all working now. :slight_smile:

David

On Friday, 6 June 2014 08:20:05 UTC+1, Lukas Zapletal wrote:

So, the big question is which is the latest stable version of puppet
that I
can use with Foreman 1.5?

Hello,

we do support most of Puppet versions. There are some exceptions:

Foreman :: Manual

What is the usual process is to install Foreman which pulls Puppet from
EPEL. Then you can upgrade Puppet to any other version you want (e.g.
Puppet Labs repo). Or you can do this even before the installation, our
installer is compatible with most versions - see the table above.


Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman


You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, 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.