Issue #16445 has been updated by eric sorenson. Status changed from Unreviewed to Closed
Ruby 1.9.x support is shaky under 2.7 and is really only supported in Puppet 3. The iconv error is fixed under Puppet 3 and the args error does not occur. ---------------------------------------- Bug #16445: parseonly error https://projects.puppetlabs.com/issues/16445#change-71554 Author: L Harris Status: Closed Priority: Normal Assignee: Category: Target version: Affected Puppet version: 2.7.12 Keywords: parseonly Branch: puppet --parseonly manifests/nodes.pp /etc/puppet/vendor/gems/ruby/1.9.1/gems/puppet-2.7.12/lib/puppet/external/pson/pure.rb:7:in `<module:PSON>': iconv will be deprecated in the future, use String#encode instead. Could not parse options: wrong number of arguments (1 for 0) ruby version: 1.9.3p0 (2011-10-30) [x86_64-linux] This happens regardless of which file I attempt to check. Not really worried about the iconv error because we get it everytime we run puppet no matter what we're doing. The problem seems to be the "Could not parse options: wrong number of arguments (1 for 0)" error. ruby --debug /etc/puppet/bin/puppet --parseonly gold/manifests/nodes.pp indicates the problem is in /etc/puppet/vendor/gems/ruby/1.9.1/gems/puppet-2.7.12/lib/puppet/application.rb:363 -- 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.
