Issue #5214 has been updated by Nigel Kersten. Status changed from Unreviewed to Accepted
---------------------------------------- Bug #5214: Puppet module not synchronising when metadata.json exists https://projects.puppetlabs.com/issues/5214 Author: Ken Barber Status: Accepted Priority: Normal Assignee: Category: modules Target version: Affected Puppet version: 2.6.2 Keywords: metadata.json Branch: I'm having trouble with modules that are skipped over during synchronisation when metadata.json exists. This metadata.json is created by the puppet-module-tool not by hand. See here: r...@puppet1:~/Development# /var/lib/gems/1.8/bin/puppet-module build puppet-iptables ====================================================== Building /root/Development/puppet-iptables for release ------------------------------------------------------ Done. Built: puppet-iptables/pkg/bobsh-iptables-1.2.0.tar.gz r...@puppet1:~/Development# mv puppet-iptables/pkg/bobsh-iptables-1.2.0 /etc/puppet/modules/bobsh-iptables r...@puppet1:~/Development# puppet agent -t info: Retrieving plugin info: Caching catalog for puppet1.hdm.bob.sh info: Applying configuration version '1289054726' notice: Finished catalog run in 3.33 seconds r...@puppet1:~/Development# rm /etc/puppet/modules/bobsh-iptables/metadata.json r...@puppet1:~/Development# puppet agent -t info: Retrieving plugin notice: /File[/var/lib/puppet/lib/puppet/test]/ensure: created notice: /File[/var/lib/puppet/lib/puppet/test/iptables.rb]/ensure: defined content as '{md5}b079e461bf96bd1194fb72abb8802515' notice: /File[/var/lib/puppet/lib/puppet/type/iptables.rb]/ensure: defined content as '{md5}66481c7e3fb362d3448509e1e7f7fb35' info: Loading downloaded plugin /var/lib/puppet/lib/puppet/test/iptables.rb err: Could not load downloaded file /var/lib/puppet/lib/puppet/test/iptables.rb: no such file to load -- puppettest info: Loading downloaded plugin /var/lib/puppet/lib/puppet/type/iptables.rb info: Caching catalog for puppet1.hdm.bob.sh info: Applying configuration version '1289054726' notice: /Stage[main]/Netperf/Service[netperf]/enable: enable changed 'true' to 'false' notice: Finished catalog run in 3.35 seconds 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 :-). -- 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.
