thr3ads.net - Puppet users - [Puppet Users] what is the right way to ensure specific version installed on puppet agent? [Dec 2013]

If this information is useful, please help other people find it:
Share via:

shlo.afgin@gmail.com

2013-Dec-04 07:19 UTC

[Puppet Users] what is the right way to ensure specific version installed on puppet agent?

Hi,

I wanted to install mysql-5.1.66 and make sure mysql-5.5.34 removed so I 
make a init.pp file and put in it:
class mysql {
    package { ''mysql'':
        ensure => "5.1.66-2.el6_3", 
        require => [Package[''mysql-libs''], 
                    Package[''compat-mysql''], 
                    Package[''mysql-5.5.34'']],
    }

    package { ''mysql-libs'':
    provider => ''yum'',
    ensure => ''purged'',
    }

    package { ''compat-mysql'':
    provider => ''yum'',
    ensure => ''absent'',
    }

    package { ''mysql-5.5.34'':
    provider => ''yum'',
    ensure => ''absent'',
    }
} 

When I test it before, two weeks ago, it work okay. It remove mysql-5.5.34 
and install mysql-5.1.66.
Today I saw the puppet agent don''t have mysql install at all.
I tried to install it from the Unix command line  and got:

*No package mysql-server-5.1.66-2.el6_3 available.Error: Nothing to do*

I believe that this version of mysql removed from the repository because 
it''s old, but I don''t want the old version to delete from my
puppet agent.
I want my puppet agent to have mysql-5.1.66 even that it not exist in the 
repository.
Is it because the puppet did not find mysql in the repository so it delete 
it from my agent? or I''m doing something wrong?

Thanks.

 

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/d2b2b204-506f-4467-8727-f453e8632229%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

jcbollinger

2013-Dec-04 14:56 UTC

head link

[Puppet Users] Re: what is the right way to ensure specific version installed on puppet agent?

On Wednesday, December 4, 2013 1:19:55 AM UTC-6, shlo....@gmail.com
wrote:>
>
>
> Hi,
>
> I wanted to install mysql-5.1.66 and make sure mysql-5.5.34 removed so I 
> make a init.pp file and put in it:
> class mysql {
>     package { ''mysql'':
>         ensure => "5.1.66-2.el6_3", 
>         require => [Package[''mysql-libs''], 
>                     Package[''compat-mysql''], 
>                     Package[''mysql-5.5.34'']],
>     }
>
>     package { ''mysql-libs'':
>     provider => ''yum'',
>     ensure => ''purged'',
>     }
>
>     package { ''compat-mysql'':
>     provider => ''yum'',
>     ensure => ''absent'',
>     }
>
>     package { ''mysql-5.5.34'':
>     provider => ''yum'',
>     ensure => ''absent'',
>     }
>

That last bit is useless, except inasmuch as there is a (definitely 
useless) reference to
Package[''''mysql-5.5.34''''] earlier. 
Puppet''s RPM and
YUM package providers will recognize <rpm name> and <rpm
name>.<arch> as
package names.  Ensuring Package[''mysql-5.5.34''] absent is
always a no-op
because although Package[''mysql''] might have version 5.5.34,
that''s doesn''t
make it a package *named* "mysql-5.5.34".

Moreover, this isn''t an issue for the vast majority of RPM packages, 
because few RPMs accommodate multiple versions of the same package 
installed.  Unless you''re dealing with custom-packaged RPMs
specifically
built to accommodate multiple versions -- and it doesn''t look like you
are
-- your earlier version-specific declaration of package "mysql" should
be
sufficient to ensure that the only version of the "mysql" package is
the
one you specify (5.1.66-2.el6_3).

> } 
>
> When I test it before, two weeks ago, it work okay. It remove mysql-5.5.34 
> and install mysql-5.1.66.
> Today I saw the puppet agent don''t have mysql install at all.
> I tried to install it from the Unix command line  and got:
>
> *No package mysql-server-5.1.66-2.el6_3 available.Error: Nothing to do*
>
> I believe that this version of mysql removed from the repository because 
> it''s old, but I don''t want the old version to delete from
my puppet agent.
> I want my puppet agent to have mysql-5.1.66 even that it not exist in the 
> repository.
> Is it because the puppet did not find mysql in the repository so it delete 
> it from my agent?
>

No.

> or I''m doing something wrong?
>
>
Yes.

Your package declarations have a hidden inconsistency that Puppet is unable 
to diagnose.  You specify that package "mysql-libs" must be purged,
but
that''s not actually what you want, because packages mysql and
mysql-server
depend on mysql-libs.  By ensuring mysql-libs purged, you force it and all 
packages that depend on it to be removed (if mysql-libs is present) every 
time the agent runs.  *That''s* why mysql-5.1.66 and mysql-server-5.1.66
got
removed.  It is surely not what you actually want, even if the mysql-5.1.66 
packages were still available in your configured repositories.  (And this 
is yet another reason why the declaration of package "mysql-5.5.34" is
useless.)

You have committed one of the classic Puppet blunders: writing manifests 
that focus on state transitions instead of on the desired target state.  I 
say that because the only reason I can imaging for declaring mysql-libs 
purged is to facilitate downgrading mysql to version 5.1.66 from a later 
version.

There are several things you should do:

   1. Create and maintain a local package repository for at least those 
   packages you depend upon, plus their dependencies.  Myself, I maintain a 
   complete local mirror of all the essential repositories I depend on.  There 
   are multiple advantages, but the most relevant one here is that you can 
   avoid packages being yanked out from under you.
   2. Remove the inconsistency in your declarations.

There are several approaches to (2), but I''d recommend creating a
custom
fact to report the installed version of mysql-libs, and making its purge 
conditional on that value.  The Puppet side might look like this:

class mysql {
  $target_version = ''5.1.66''
  $target_release = ''2.el6_3''

  package { ''mysql'': ensure =>
"${target_version}-${target_release)" }

  # assumes that mysql-libs version must match mysql version;
  # $::mysql_libs_version is a custom fact you must provide:
  if $::mysql_libs_version != '''' and
versioncmp($target_version,
$::mysql_libs_version) < 0 {
    package { ''mysql-libs'':
      ensure => ''purged''
      before => Package[''mysql'']
    }
  }

  package { ''compat-mysql'': ensure =>
''absent'' }
}

Note that there is no need for a resource relationship between 
Package[''compat-mysql''] and
Package[''mysql''], because it doesn''t matter in
which relative order these resources are applied.  Note also that there is 
no longer any declaration of a package "mysql-5.5.34"; it is unneeded.

Additionally, note that it is not normally necessary to explicitly specify 
a provider in your resource declarations.

See http://docs.puppetlabs.com/guides/custom_facts.html for information 
about writing and distributing custom facts.

John

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/9b0fd6fb-8a76-4eb7-8ad1-5c4993c3421c%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

shlo.afgin@gmail.com

2013-Dec-05 07:31 UTC

head link

[Puppet Users] Re: what is the right way to ensure specific version installed on puppet agent?

Thank you very much for your detailed answer.
 

On Wednesday, December 4, 2013 4:56:34 PM UTC+2, jcbollinger
wrote:>
>
>
> On Wednesday, December 4, 2013 1:19:55 AM UTC-6, shlo....@gmail.com wrote:
>>
>>
>>
>> Hi,
>>
>> I wanted to install mysql-5.1.66 and make sure mysql-5.5.34 removed so
I
>> make a init.pp file and put in it:
>> class mysql {
>>     package { ''mysql'':
>>         ensure => "5.1.66-2.el6_3", 
>>         require => [Package[''mysql-libs''], 
>>                     Package[''compat-mysql''], 
>>                     Package[''mysql-5.5.34'']],
>>     }
>>
>>     package { ''mysql-libs'':
>>     provider => ''yum'',
>>     ensure => ''purged'',
>>     }
>>
>>     package { ''compat-mysql'':
>>     provider => ''yum'',
>>     ensure => ''absent'',
>>     }
>>
>>     package { ''mysql-5.5.34'':
>>     provider => ''yum'',
>>     ensure => ''absent'',
>>     }
>>
>
>
> That last bit is useless, except inasmuch as there is a (definitely 
> useless) reference to
Package[''''mysql-5.5.34''''] earlier. 
Puppet''s RPM and
> YUM package providers will recognize <rpm name> and <rpm
name>.<arch> as
> package names.  Ensuring Package[''mysql-5.5.34''] absent
is always a no-op
> because although Package[''mysql''] might have version
5.5.34, that''s doesn''t
> make it a package *named* "mysql-5.5.34".
>
> Moreover, this isn''t an issue for the vast majority of RPM
packages,
> because few RPMs accommodate multiple versions of the same package 
> installed.  Unless you''re dealing with custom-packaged RPMs
specifically
> built to accommodate multiple versions -- and it doesn''t look like
you are
> -- your earlier version-specific declaration of package "mysql"
should be
> sufficient to ensure that the only version of the "mysql" package
is the
> one you specify (5.1.66-2.el6_3).
>
>  
>
>> } 
>>
>> When I test it before, two weeks ago, it work okay. It remove 
>> mysql-5.5.34 and install mysql-5.1.66.
>> Today I saw the puppet agent don''t have mysql install at all.
>> I tried to install it from the Unix command line  and got:
>>
>> *No package mysql-server-5.1.66-2.el6_3 available.Error: Nothing to do*
>>
>> I believe that this version of mysql removed from the repository
because
>> it''s old, but I don''t want the old version to delete
from my puppet agent.
>> I want my puppet agent to have mysql-5.1.66 even that it not exist in
the
>> repository.
>> Is it because the puppet did not find mysql in the repository so it 
>> delete it from my agent?
>>
>
>
> No.
>
>  
>
>> or I''m doing something wrong?
>>
>>
>
> Yes.
>
> Your package declarations have a hidden inconsistency that Puppet is 
> unable to diagnose.  You specify that package "mysql-libs" must
be purged,
> but that''s not actually what you want, because packages mysql and 
> mysql-server depend on mysql-libs.  By ensuring mysql-libs purged, you 
> force it and all packages that depend on it to be removed (if mysql-libs is
> present) every time the agent runs.  *That''s* why mysql-5.1.66 and
> mysql-server-5.1.66 got removed.  It is surely not what you actually want, 
> even if the mysql-5.1.66 packages were still available in your configured 
> repositories.  (And this is yet another reason why the declaration of 
> package "mysql-5.5.34" is useless.)
>
> You have committed one of the classic Puppet blunders: writing manifests 
> that focus on state transitions instead of on the desired target state.  I 
> say that because the only reason I can imaging for declaring mysql-libs 
> purged is to facilitate downgrading mysql to version 5.1.66 from a later 
> version.
>
> There are several things you should do:
>
>    1. Create and maintain a local package repository for at least those 
>    packages you depend upon, plus their dependencies.  Myself, I maintain a
>    complete local mirror of all the essential repositories I depend on. 
There
>    are multiple advantages, but the most relevant one here is that you can 
>    avoid packages being yanked out from under you.
>    2. Remove the inconsistency in your declarations.
>
> There are several approaches to (2), but I''d recommend creating a
custom
> fact to report the installed version of mysql-libs, and making its purge 
> conditional on that value.  The Puppet side might look like this:
>
> class mysql {
>   $target_version = ''5.1.66''
>   $target_release = ''2.el6_3''
>
>   package { ''mysql'': ensure =>
"${target_version}-${target_release)" }
>
>   # assumes that mysql-libs version must match mysql version;
>   # $::mysql_libs_version is a custom fact you must provide:
>   if $::mysql_libs_version != '''' and
versioncmp($target_version,
> $::mysql_libs_version) < 0 {
>     package { ''mysql-libs'':
>       ensure => ''purged''
>       before => Package[''mysql'']
>     }
>   }
>
>   package { ''compat-mysql'': ensure =>
''absent'' }
> }
>
> Note that there is no need for a resource relationship between 
> Package[''compat-mysql''] and
Package[''mysql''], because it doesn''t matter in
> which relative order these resources are applied.  Note also that there is 
> no longer any declaration of a package "mysql-5.5.34"; it is
unneeded.
>
> Additionally, note that it is not normally necessary to explicitly specify 
> a provider in your resource declarations.
>
> See http://docs.puppetlabs.com/guides/custom_facts.html for information 
> about writing and distributing custom facts.
>
>
> John
>
>
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/fee9f691-420b-46bb-83f5-b72c727db617%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Puppet users - Dec 2013 - what is the right way to ensure specific version installed on puppet agent?

[Puppet Users] what is the right way to ensure specific version installed on puppet agent?

[Puppet Users] Re: what is the right way to ensure specific version installed on puppet agent?

[Puppet Users] Re: what is the right way to ensure specific version installed on puppet agent?