The Puppet Labs Issue Tracker has Moved:

Refactor #5870

Handle failure case where FQDN is undefined in defaults.rb better

Added by Daniel Pittman over 3 years ago. Updated over 2 years ago.

Status:AcceptedStart date:01/12/2011
Priority:NormalDue date:
Assignee:-% Done:


Target version:3.x
Affected Puppet version:2.6.4 Branch:

We've Moved!

Ticket tracking is now hosted in JIRA:

This ticket may be automatically exported to the PUP project on JIRA using the button below:


At the moment Puppet uses the ‘hostname’ and ‘domainname’ facts to derive an FQDN, and uses that in turn to seed the certname values.

However, in the event that those values don’t return sensible things the fqdn value in defaults.rb wound up as nil – and this ended up causing a failure way down the chain in the validation of the certname field. It would be much, much better to detect this at the time we derive the invalid FQDN and report it along with a sensible error at that stage.


#1 Updated by Nigel Kersten about 3 years ago

  • Status changed from Unreviewed to Accepted
  • Target version set to 2.6.x

#2 Updated by Nigel Kersten over 2 years ago

  • Target version changed from 2.6.x to 3.x

Also available in: Atom PDF