Ubuntu 12.04 LTS - error calling module

[Ventz Petkov]

Hi,

Running into an interesting problem:
(on Ubuntu 12.04 LTS, with build-essential installed)

puppet agent -t --environment dev

Info: Retrieving plugin
Notice: /File[/var/lib/puppet/lib/facter]/ensure: created
Notice: /File[/var/lib/puppet/lib/facter/vmwaretools_version.rb]/ensure: defined content as '{md5}175fac1f68337cdebe52f36642f24a93'
Info: Loading facts in /var/lib/puppet/lib/facter/vmwaretools_version.rb
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class vmwaretools for testnode.domain.tld on node testnode.domain.tld
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

I am calling it with just: "include vmwaretools" inside a:
"test_default", for which the init.pp looks like this:

class test_default {
include vmwaretools
}

Clearly it's finding the class since it loads the vmwaretools_version.rb

[Adam White]

So you have a nodes.pp with:

node 'testnode' {
    include test_default
}

and an init.pp:

class test_default {
    include vmwaretools
}

Is that correct?

[Ventz Petkov]

For the node, I have it as a 'default' since this is my dev area:

node default {
    include test_default
}

But yea, for the class, it's just that "test_default" with an include vmwaretools

The only thing that I can see being difference is the "environments", which are being pulled from git into paths:
/etc/environments/{dev,testing, master}

But other than that, at the end of the day, the correct set of files are there, and puppet.conf has the correct module paths loaded. I am pretty confident it's not the setup/paths, since other modules work.

Let me know if I can provide any other information, run any additional tests.

[Craig Watson]

Can you run Puppet as:

puppet agent --test --debug --environment dev

You can then see what's being done on the back-end by Puppet - can you Gist/post the output?

[Ventz Petkov]

https://gist.github.com/ventz/7e0bfba42adfd141248e

[Craig Watson]

@ventz - sorry for the delay in getting to this - can you confirm that other classes load OK? /etc/environments is a slightly non-standard path.

[Ventz Petkov]

Hi,

No problem - yea, everything else seems to load without problems. My issue
is that I am not sure how to debug this. I haven't run into this with any
other modules, and everything looks OK on the surface.

On Tue, Jul 16, 2013 at 8:16 AM, Craig Watson [e-mail]:

@ventz https://github.com/ventz - sorry for the delay in getting to
this - can you confirm that other classes load OK? /etc/environments is a
slightly non-standard path.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/13#issuecomment-21037966
.

-Ventz
http://vpetkov.net

[Craig Watson]

@ventz Hey, have you managed to debug this any further? Unfortunately I can't seem to replicate it, so I'll close and mark as "wontfix" for now unless you have any objections?

[Ventz Petkov]

Hi - sorry for the delayed response. I haven't had any free time to look into this. Please close it, and I'll try to send you any info that I find when I get some time to work on this. Thanks,-Ventz From: Craig WatsonSent: Tuesday, September 17, 2013 5:15 PMTo: craigwatson/puppet-vmwaretoolsReply To: craigwatson/puppet-vmwaretoolsCc: Ventz PetkovSubject: Re: [puppet-vmwaretools] Ubuntu 12.04 LTS - error calling module (#13)@ventz Hey, have you managed to debug this any further? Unfortunately I can't seem to replicate it, so I'll close and mark as "wontfix" for now unless you have any objections?

—Reply to this email directly or view it on GitHub.

[Ventz Petkov]

Craig -- it looks like the latest version from github works now.

Using r10k environment with a Puppetfile containing:
mod 'vmwaretools',
:git => 'https://github.com/craigwatson/puppet-vmwaretools'

Testing it with just initialize a simple "init.pp" with:
class { 'vmwaretools': }

Seems to run without problems.

[Craig Watson]

Awesome, thanks for letting me know :)