On Mon, 6 Feb 2012, Craig White wrote:
On Feb 6, 2012, at 11:10 AM, Clay B. wrote:
I have found that using Puppet 2.6.2 on my master and running Puppet 2.6.12 on
my clients seems to have resolved this issue, while 2.7 was failing.
Perhaps Puppet defined resources have different semantics in 2.7?
----
I can't answer that but your 'master' should always be at least equal to or
higher than the version of all clients.
Craig
Unfortunately, it seems to be the state of the 2.6 packages available for
Centos and Debian via puppetlab's Yum and Debian's Apt repos; but at least
they seem to play nicely -- so far. (It seems apt.puppetlabs.org only has
2.7 versions.)
Thank you Puppet-folk for providing the repositories!
(With vendor defaults and Puppetlab's repos.)
[admin@rpmhost ~]$ yum list puppet|grep 2.6
Repository 'puppetlabs' is missing name in configuration, using id
puppet.noarch 2.6.12-2.el5 installed
admin@debhost:~$ apt-cache policy puppet|grep 2.6
Installed: 2.6.2-5+squeeze3
*** 2.6.2-5+squeeze3 0
2.6.2-5+squeeze1 0
-Clay
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-users@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.
