I was wondering if I could get help.
on client
[root@linux ~]# puppetd --test --verbose
info: Caching catalog at /var/lib/puppet/localconfig.yaml
notice: Starting catalog run
err: //Node[basenode]/motd/Package[motd]/ensure: change from absent to
latest failed: Could not update: Could not find package motd at
/etc/puppet/modules/motd/manifests/init.pp:5
notice: //Node[basenode]/motd/File[/etc/motd]: Dependency package[motd] has
1 failures
notice: Finished catalog run in 9.68 seconds
on puppetmaster
# /etc/puppet/modules/motd/manifests/init.pp
class motd {
package { motd: ensure => latest }
file { "/etc/motd":
owner => root,
group => root,
mode => 440,
source => "puppet:///motd/motd",
require => Package["motd"],
}
}
Thanks
Cory McKee
--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
Hi Cory, Running the puppet client with --debug will show the underlying system calls that are failing. It looks like the package manager cannot find any packages called motd (I dont think there is a package called motd, this is a login function). Also, a tip. You can use the "puppet" command to test manifests without having to worry about running a client/server. just run>puppet MANIFEST.ppfor this to work, you need to include the class in the pp file. regards, Dan On Mon, Nov 16, 2009 at 12:07 PM, Cory mckee <redhawk1973@gmail.com> wrote:> I was wondering if I could get help. > > on client > > > [root@linux ~]# puppetd --test --verbose > info: Caching catalog at /var/lib/puppet/localconfig.yaml > notice: Starting catalog run > err: //Node[basenode]/motd/Package[motd]/ensure: change from absent to > latest failed: Could not update: Could not find package motd at > /etc/puppet/modules/motd/manifests/init.pp:5 > notice: //Node[basenode]/motd/File[/etc/motd]: Dependency package[motd] has > 1 failures > notice: Finished catalog run in 9.68 seconds > > on puppetmaster > > # /etc/puppet/modules/motd/manifests/init.pp > > class motd { > > package { motd: ensure => latest } > > file { "/etc/motd": > owner => root, > group => root, > mode => 440, > source => "puppet:///motd/motd", > require => Package["motd"], > } > } > > > > Thanks > Cory McKee > > > >--~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Le lundi 16 novembre 2009 à 13:07 -0500, Cory mckee a écrit :> I was wondering if I could get help. > > on client > > > [root@linux ~]# puppetd --test --verbose > info: Caching catalog at /var/lib/puppet/localconfig.yaml > notice: Starting catalog run > err: //Node[basenode]/motd/Package[motd]/ensure: change from absent to > latest failed: Could not update: Could not find package motd > at /etc/puppet/modules/motd/manifests/init.pp:5 > notice: //Node[basenode]/motd/File[/etc/motd]: Dependency > package[motd] has 1 failures > notice: Finished catalog run in 9.68 seconds > > on puppetmaster > > # /etc/puppet/modules/motd/manifests/init.pp > > class motd { > > package { motd: ensure => latest } > > file { "/etc/motd": > owner => root, > group => root, > mode => 440, > source => "puppet:///motd/motd", > require => Package["motd"], > } > } > >Looks like your package management system does not know about any package named "motd". Which distro is this ? Nico.