> Hmm, no luck using ntp::ntp instead of ntp. The problem seems to be in
> importing rather than including. I tried using ntp, ntp::ntp, and the
> full path /etc/puppet/modules/ntp/manifests/init.pp.
>
> It always fails with:
>
> err: Could not retrieve catalog from remote server: Error 400 on SERVER:
> Could not parse for environment production: No file(s) found for import
> of 'ntp' at /etc/puppet/manifests/site.pp:6
Hi Jonathan,
You shouldn't need to "import" your ntp module as Puppet should auto
load it if the pathing is all correct, which it looks like it is.
Remote the 'import "ntp"' line from your site.pp:
In site.pp:
import "nodes.pp"
In nodes.pp:
node 'espresso.resnet.bris.ac.uk' {
include ntp
}
Then run the evaltrace on your node to see if your module and
resources are there. Like Felix, an import of "nodes" seems is strange
to me - maybe Puppet will implicitly add a .pp extension for files in
the CWD? You should not need to explicitly import your module
manifests, using include and Puppet with a correct modulepath should
find it.
-Luke
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
