Hi Folks,
I am fairly new to using Puppet, but am trying to use it to control
production servers running:
- CentOS 5.5
- Puppet 2.6.3
- Yum 3.2.22
We would like to specify that certain versions of packages be loaded
on a system. Our requirement is to have fixed versions of all critical
packages upon which our applications depend. We do not want any
surprises due to unplanned updates to the latest and greatest release
of a critical software dependency.
We are using manifests with a package resource like:
package { "mysql": ensure => "5.0.77-4.el5_5.3", }
The problem we run into is that when one server is loaded the manifest
and puppet works like a charm. If some time passes and a later version
of a package is available in the yum repository and we attempt to load
another server using the same puppet catalog; then puppet will
complain that it is unable to load the specified version in the
manifest, because it found a later version via yum (e.g.
mysql-5.0.77-4.el5_5.4). The error message is shown below:
err: /Stage[base]/Centos-server-pack/Package[mysql]/ensure: change
from 5.0.77-4.el5_5.4 to 5.0.77-4.el5_5.3 failed: Could not update:
Failed to update to version 5.0.77-4.el5_5.3, got version
5.0.77-4.el5_5.4 instead at /etc/puppet/modules/centos-base-pkg/
manifests/init.pp:288
Has anyone else run into this problem or have an suggestions?
Thanks in advance for your advice.
Andy
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
