Issue #5109 has been updated by Ken Barber.

File puppetmasterd-output-bug5109.txt added
Status changed from Duplicate to Re-opened

Peter - I'm not so sure this is a duplicate. This was reported to me by a user 
of the puppet module bobsh-iptables ...

http://issues.bob.sh/jira/browse/IPT-5

I'm seeing the same issue on 2.6.2 even though it has the fix applied in #4142 
(ie. PSON instead of JSON). So I believe we are dealing with another issue here.

I also do not get this error:

    err: expected next name, value pair in object at '}
    '!

As shown in #4142.

I tried using the gem version of puppet-module and the latest revision from 
github - both the same results. I also tried tag 0.3.0, 0.2.9 and 0.2.8 to see 
if it was something new puppet-module was doing. The module is simply skipped 
over in 2.6.2 until metadata.json is removed.

I can confirm that the REST call to:

    GET 
/production/file_metadatas/plugins?&checksum_type=md5&ignore=---+%0A++-+.svn%0A++-+CVS%0A++-+.git&recurse=true&links=manage

Skips over the module completely.

I was able to confirm this behaviour with bobsh-ssh, bobsh-iptables and a new 
test module I created.

I've attached the output of puppetmasterd --trace --debug --no-daemonize.

I'm running Debian Squeeze using the Puppet 2.6.2 package they provide. Ruby 
1.8.7 on an x86_64 machine. The problem was also reported in 0.25.5 by Don 
Harden in the link to my issues page above as you can see - I haven't confirmed 
this myself on my machines.

A good test module to try this with is my bob.sh module: 
http://forge.puppetlabs.com/system/releases/b/bobsh/bobsh-iptables-1.2.0.tar.gz

If you think I am in error - please let me know. Happy to help with any 
testing. Cheers :-).
----------------------------------------
Bug #5109: puppet-module-tool failes with .json file in directory
https://projects.puppetlabs.com/issues/5109

Author: Christopher Lee
Status: Re-opened
Priority: Normal
Assignee: 
Category: modules
Target version: 2.6.x
Affected Puppet version: 2.6.2
Keywords: 
Branch: 


When creating a new module with puppet-module-tool I get an error unless I 
remove the metadata.json file.  Here are the steps I use:

    > puppet-module generate cml-blank

Run a test:

    [r...@xxxx puppet]# puppet agent --test --verbose --noop
    err: Could not retrieve catalog from remote server: Error 400 on SERVER: No 
source module metadata provided for blank at /opt/puppet/LAB/site.pp:7 on node 
myservername.com
    warning: Not using cache on failed catalog
    err: Could not retrieve catalog; skipping run

I then remove the metadata.json file and run again:

    [r...@xxxxxx puppet]# puppet agent --test --verbose --noop
    info: Caching catalog for myservername.com
    info: Applying configuration version '1288139357'
    notice: Finished catalog run in 0.02 seconds




-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" 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-bugs?hl=en.

Reply via email to