The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Bug #1117

Puppetmaster w/ Mongrel barfs when clients lack PTR records

Added by Philip Walls almost 7 years ago. Updated almost 7 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:Puppet Community% Done:

0%

Category:-
Target version:0.24.3
Affected Puppet version:0.25.4 Branch:
Keywords:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This issue is currently not available for export. If you are experiencing the issue described below, please file a new ticket in JIRA. Once a new ticket has been created, please add a link to it that points back to this Redmine ticket.


Description

I’m not sure if this was intentional or not, but adding a simple rescue block around the Resolv portion results in my clients being able to do a completely successful Puppet run. Patch attached.

puppet_fix_mongrel_without_ptr.2.diff Magnifier (566 Bytes) Philip Walls, 03/07/2008 03:16 am

History

#1 Updated by Philip Walls almost 7 years ago

I probably should have specified a particular exception in the rescue block. I’m not sure what Resolv throws and I don’t have the time to find out right now. Hopefully the attached patch is sufficient.

#2 Updated by Andrew Shafer almost 7 years ago

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

This is fixed

commit 7a9aae84805e415de090f0ce9be04beb8435e117 Author: Luke Kanies luke@madstop.com Date: Sat Jan 19 14:08:44 2008 -0600

Wrapping the Resolv call in the mongrel server so if it
fails it doesn't kill the server.

Also available in: Atom PDF