Bug #886

Puppetdoc returns an error that the nodoc method is undefined

Added by James Turnbull over 4 years ago. Updated over 4 years ago.

Status:Closed Start date:
Priority:Low Due date:
Assignee:Puppet Community % Done:

0%
Category:-
Target version:0.24.0
Affected Puppet version:0.25.4 Branch:
Keywords:
Votes: 0

Description

When running latest puppetdoc (both in 0.23.2 and Git) the following error is generated:

$ puppetdoc
usr/lib/ruby/site_ruby/1.8/puppet/reference/type.rb:114:in @generate': undefined method @nodoc' for Puppet::Type::Cron::Command:Class (NoMethodError)
        from /usr/lib/ruby/site_ruby/1.8/puppet/reference/type.rb:110:in @reject'
        from /usr/lib/ruby/site_ruby/1.8/puppet/reference/type.rb:110:in @generate'
        from /usr/lib/ruby/site_ruby/1.8/puppet/reference/type.rb:90:in @each'
        from /usr/lib/ruby/site_ruby/1.8/puppet/reference/type.rb:90:in @generate'
        from /usr/lib/ruby/site_ruby/1.8/puppet/util/reference.rb:153:in @to_rest'
        from /usr/bin/puppetdoc:135:in @send'
        from /usr/bin/puppetdoc:135
        from /usr/bin/puppetdoc:131:in @each'
        from /usr/bin/puppetdoc:131

History

#1
Updated by Tim Stoop over 4 years ago

I can confirm this error in the Debian unstable packages too. I’m guessing it’s simply a uncaught ‘exception’ when running puppetdoc without an argument. Should be caught and probably be redirected to —help. Guessing that’s trivial to do.

#2
Updated by Luke Kanies over 4 years ago

  • Status changed from 1 to Closed
  • 7 set to fixed

Fixed in commit:b745f04d936575d3a1a54b98bccc4b49de734531.

Also available in: Atom PDF