On Nov 27, 2011, at 5:22 PM, Nigel Kersten wrote:
> On Sun, Nov 27, 2011 at 2:48 PM, Jo Rhett wrote:
> Assuming that what you say above is right, I would suggest that showing the
> error only once is only useful for single-digit puppet installations. The
> problem here is that I have 500+ nodes.
On Sun, Nov 27, 2011 at 2:48 PM, Jo Rhett wrote:
> On Sat, Nov 26, 2011 at 7:25 PM, Jo Rhett wrote:
>
>> On Nov 25, 2011, at 11:59 AM, Peter Berghold wrote:
>>
>> err: Could not retrieve catalog from remote server: Error 400 on SERVER:
>> Could not find class adminscripts::getvpsnodes for
>> slcc
> On Sat, Nov 26, 2011 at 7:25 PM, Jo Rhett wrote:
> On Nov 25, 2011, at 11:59 AM, Peter Berghold wrote:
>> err: Could not retrieve catalog from remote server: Error 400 on SERVER:
>> Could not find class adminscripts::getvpsnodes for
>> slccrepos0.slc.sharkrivertech.com at
>> /etc/puppet/manif
On Sat, Nov 26, 2011 at 7:25 PM, Jo Rhett wrote:
> On Nov 25, 2011, at 11:59 AM, Peter Berghold wrote:
>
> err: Could not retrieve catalog from remote server: Error 400 on SERVER:
> Could not find class adminscripts::getvpsnodes for
> slccrepos0.slc.sharkrivertech.com at
> /etc/puppet/manifests/n
On Nov 25, 2011, at 11:59 AM, Peter Berghold wrote:
> err: Could not retrieve catalog from remote server: Error 400 on SERVER:
> Could not find class adminscripts::getvpsnodes for
> slccrepos0.slc.sharkrivertech.com at
> /etc/puppet/manifests/nodes/slccrepos0.pp:4 on node
> slccrepos0.slc.shark
class foo { ... } -> modulepath/foo/manifests/init.pp
> class foo::bar { ... } -> modulepath/foo/manifests/bar.pp
>
> and then you should be able to remove all the import *.pp statements.
>
> There's been a bit of grief expressed over this bug, so I'd like to
> reiterate that this wasn't a delibera
On Fri, Nov 25, 2011 at 12:46 PM, Peter Berghold wrote:
>
>
> On Fri, Nov 25, 2011 at 3:32 PM, Nigel Kersten 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 bea
I take that back. Seems I was running the wrong master. Started running
the proper master and the problem is back:
Here is what I'm seeing in the logged output:
debug: importing '/etc/puppet/modules/adminscripts/manifests/init.pp' in
environment production
debug: importing
'/etc/puppet/modules
OK: ran the master in verbose debug mode and the behavior changed. (!)
Seems the real problem was some stuff in the earlier stages (just updated
my puppet master the other day) was and the messages were masking the
problem.
I had some statements in my templates.pp file such as
class { trusted
ran and got:
puppet --debug -v --parseonly init.pp
debug: importing
'/home/peter/src2/puppet-cfg/modules/adminscripts/manifests/getvpsnodes.pp'
debug: importing
'/home/peter/src2/puppet-cfg/modules/adminscripts/manifests/init.pp'
On Fri, Nov 25, 2011 at 3:45 PM, Denmat wrote:
> Hi,
>
> The fol
- Original Message -
>
>
> 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
seconded, good information up front makes it all easier.
I could
Hi,
The following will fail wont it? The source path is wrong.
source => "puppet://puppet/syscripts/getVPSNodes.pl",
I can't check the class myself but do the .pp files parse correctly? Use the
--parseonly or the validate command to check. It maybe failing to parse one of
the files.
Cheers,
On Fri, Nov 25, 2011 at 3:32 PM, Nigel Kersten 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/
On Fri, Nov 25, 2011 at 11:59 AM, Peter Berghold wrote:
>
>
> I have this module with the following structure.
>
> adminscripts
> ├── facter
> ├── files
> │ └── getVPSNodes.pl
> ├── lib
> │ └── puppet
> │ ├── parser
> │ ├── provider
> │ └── type
> ├── manifests
> │ ├── clas
I have this module with the following structure.
adminscripts
├── facter
├── files
│ └── getVPSNodes.pl
├── lib
│ └── puppet
│ ├── parser
│ ├── provider
│ └── type
├── manifests
│ ├── classes
│ ├── defines
│ ├── getvpsnodes.pp
│ └── init.pp
└── templates
The file g
15 matches
Mail list logo
