Bug #417

puppetd behaved badly due to defect manifest

Added by Mario Martelli over 5 years ago. Updated about 5 years ago.

Status:Closed Start date:
Priority:Normal Due date:
Assignee:Luke Kanies % Done:

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

Description

I had a “ missing in one of my manifests

  $oldkernel = $kernel ? {
    sunos => "sunos",
    linux => "linux
  }

this resulted in

err: Could not match '/mnt/sop_products/SOP_AUTOMATED_INSTALL/SOPware_$suite_version/$oldkernel"' at /var/puppetisation/puppet/conf/manifests/applications/sopware/sopware20.pp:219

on the master and the puppetd didn’t do anything anymore. After C-c I got:

/usr/local/lib/ruby/gems/1.8/gems/puppet-0.22.0/lib/puppet/networkclient.rb:77:in @freshness': Could not match '/mnt/sop_products/SOP_AUTOMATED_INSTALL/SOPware_$suite_version/$oldkernel"' at /var/puppetisation/puppet/conf/manifests/applications/sopware/sopware20.pp:219 (Puppet::NetworkClientError)
        from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.22.0/lib/puppet.rb:282:in @join'
        from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.22.0/lib/puppet.rb:282:in @shutdown'
        from /usr/local/lib/ruby/1.8/timeout.rb:56:in @timeout'
        from /usr/local/lib/ruby/1.8/timeout.rb:76:in @timeout'
        from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.22.0/lib/puppet.rb:281:in @shutdown'
        from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.22.0/lib/puppet.rb:279:in @shutdown'
        from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.22.0/lib/puppet.rb:207:in @settraps'
        from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.22.0/lib/puppet/event-loop/event-loop.rb:123:in @select'
        from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.22.0/lib/puppet/event-loop/event-loop.rb:112:in @iterate'
        from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.22.0/lib/puppet/event-loop/event-loop.rb:103:in @run'
        from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.22.0/lib/puppet.rb:328:in @start'
        from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.22.0/bin/puppetd:446
        from /usr/local/bin/puppetd:18

Please note: this caused also reopening of #353

History

#1
Updated by Luke Kanies over 5 years ago

I can’t reproduce either of these problems. That is, I can’t get the failure you mention when you’re missing quotes, and I can’t get puppetd to hang as a result.

Even when I cause these failures in combination with puppetrun, I get consistent, decent behaviour.

#2
Updated by Luke Kanies over 5 years ago

I think this is not actually a problem, so I’m marking this for the grover release and will close it later unless I get confirmation.

#3
Updated by Luke Kanies about 5 years ago

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

I cannot reproduce this.

Also available in: Atom PDF