On Fri, Nov 25, 2011 at 3:32 PM, Nigel Kersten <[email protected]> wrote:
>
> As an aside, this was an awesome way to post a module autoload problem
> Peter, showing the filesystem layout and the manifest content.
>
>
the "tree" command is a beautiful thing! :-D
Do you perhaps have another adminscripts/manifests/init.pp somewhere else
> in your modulepath?
>
> Nope. only one of it's kind. In fact it was originally named
"sysscripts/..." and I moved it from that name to adminscripts. When it
was named sysscripts I got the same error and renaming it was part of my
plan to figure out why.
> Or is there a "class adminscripts { ... }" defined somewhere else that's
> been picked up by a non-autloaded filesystem layout?
>
> Is this the only version of the adminscripts::getvpsnodes class that
> exists in any of your modulepath components?
>
>
This is the only version.
> Anything unusual about the adminscripts/manifests/init.pp in this specific
> module?
>
> Here's init.pp:
import "*.pp"
import "*.pp"
class adminscripts {
case $operatingsystem {
default : { }
}
}
> This doesn't look related, but I'm curious about:
>
> source => "puppet://puppet/syscripts/getVPSNodes.pl",
>
>
OK.... just fixed that. I forgot to edit the source when I moved the
module to its new name.
> when it looks like you're also delivering it as:
>
My modules stay pretty consistent because I use a script to lay them out
and check them into SVN. In fact I never edit the modules directly on the
puppet server, but rather modify them on a laptop, check them into SVN and
have cron check out the new versions as they become available.
--
Peter L. Berghold
Owner, Shark River Technical Solutions LLC
--
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.
