On Mon, Apr 26, 2010 at 10:23 AM, Douglas Garstang
<doug.garst...@gmail.com> wrote:
> On Mon, Apr 26, 2010 at 10:20 AM, R.I.Pienaar <r...@devco.net> wrote:
>>> and I include it in every single module (shame I can't include it at
>>> site.pp). As far as I know, including one class in another does not
>>> guarantee that the other class gets evaluated first, even though the
>>> other class has a default Package{} .... or does it? Docs on this
>>> stuff in puppet are really murky.
>>
>> where do you include opsys::$operatingsystem at the moment? show us your
>> entire current code so we know.
>>
>> My intended design was that in site.pp you could do Package{ require =>
>> Class["opsys::setup"] } and retain that functionality
>
> I don't include opsys::$operatingsystem anywhere at the moment. I was
> going to start putting it every single module which seems ugly. I
> hadn't thought of the the idea of putting it in site.pp the way you
> just did... I'll give that a shot.
Actually, that's not working so well now either. I am getting:
Apr 26 10:28:56 s_...@app09.fr.xxx.com puppetd[19381]: Configuration
could not be instantiated: Could not find dependency Class[os::setup]
for Package[net-snmp] at /etc/puppet/modules/snmp/manifests/init.pp:31
my site.pp has (amongst other stuff):
Package {
require => Class["os::setup"]
}
and the os module has:
class os::centos {
Package {
provider => yum,
require => Exec["yum-clean-all"]
}
exec {
"yum-clean-all":
command => "/usr/bin/yum clean all";
}
}
class os::setup {
include "os::${operatingsystem}"
}
So, apparently the net-snmp module can't find os::setup class. Not sure why...
Doug.
--
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.
