How to master puppet version on foreman installed hosts?

Hello,

When installing or reinstalling hosts with Foreman (RHEL Kickstart
provisioning), it happens that the puppet agent (rpm puppet) which
is installed with kickstart is too new for my puppet server/foreman
combination (lastest is puppet 3.6 and I would like it to stay in 3.5).

=> How do I make it so that puppet version on installed hosts stays at
3.5 ? Does this implies creating a custom repo ? What is the best way
to deal with this ?

Thank you

JM

··· -- ------------------------------------------------------------------------ Jean-michel BARBET | Tel: +33 (0)2 51 85 84 86 Laboratoire SUBATECH Nantes France | Fax: +33 (0)2 51 85 84 79 CNRS-IN2P3/Ecole des Mines/Universite | E-Mail: barbet@subatech.in2p3.fr ------------------------------------------------------------------------

A custom repo's pretty simple, and easy to set up.

You could also usse a "yum install puppet-3.5.1" in the %post instead of
%packages. As long as that version's available (which it is from
yum.pl.com) then it'll install just that. You could also use
yum-versionlock to prevent it changing.

··· On 10/06/14 03:35, Jean-Michel Barbet wrote: > Hello, > > When installing or reinstalling hosts with Foreman (RHEL Kickstart > provisioning), it happens that the puppet agent (rpm puppet) which > is installed with kickstart is too new for my puppet server/foreman > combination (lastest is puppet 3.6 and I would like it to stay in 3.5). > > => How do I make it so that puppet version on installed hosts stays at > 3.5 ? Does this implies creating a custom repo ? What is the best way > to deal with this ?


Dominic Cleal
Red Hat Engineering

Hello,

what you can do is to take control of your repositories and update them
according to your schedule. There is a Foreman plugin called Katello
that allows you to define products, repositories, filters, schedule
synchronizations.

It leverages Pulp Project which you can use standalone as well, if you
prefer command line.

This way you can prevent this situation and your provisioning and
upgrade process will be under much better control.

LZ

··· On Tue, Jun 10, 2014 at 09:35:18AM +0200, Jean-Michel Barbet wrote: > Hello, > > When installing or reinstalling hosts with Foreman (RHEL Kickstart > provisioning), it happens that the puppet agent (rpm puppet) which > is installed with kickstart is too new for my puppet server/foreman > combination (lastest is puppet 3.6 and I would like it to stay in 3.5). > > => How do I make it so that puppet version on installed hosts stays at > 3.5 ? Does this implies creating a custom repo ? What is the best way > to deal with this ? > > Thank you > > JM > > -- > ------------------------------------------------------------------------ > Jean-michel BARBET | Tel: +33 (0)2 51 85 84 86 > Laboratoire SUBATECH Nantes France | Fax: +33 (0)2 51 85 84 79 > CNRS-IN2P3/Ecole des Mines/Universite | E-Mail: barbet@subatech.in2p3.fr > ------------------------------------------------------------------------ > > -- > 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.


Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman

This does the trick. A custom repo is not required in this case but, yes
it might get updated and I have to look at yum-versionlock.

Actually, I have yum priorities set after the installation that
currently prevent that (SL take over puppetlabs repo). This is also
sth touchy to set. I do not know what is advised here. Do people use
yum priorities ?

I looked at Pulp following Lukas'sugesstion but for me it seems a bit of
an overkill.

Thank you both.

JM

··· On 06/10/2014 02:24 PM, Dominic Cleal wrote:

A custom repo’s pretty simple, and easy to set up.

You could also usse a “yum install puppet-3.5.1” in the %post instead of
%packages. As long as that version’s available (which it is from
yum.pl.com) then it’ll install just that. You could also use
yum-versionlock to prevent it changing.

Jean-michel BARBET | Tel: +33 (0)2 51 85 84 86
Laboratoire SUBATECH Nantes France | Fax: +33 (0)2 51 85 84 79
CNRS-IN2P3/Ecole des Mines/Universite | E-Mail: barbet@subatech.in2p3.fr