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

Bug #14624

2-space indent in puppetdb.conf confuses puppet

Added by Gary Larizza almost 2 years ago. Updated almost 2 years ago.

Status:ClosedStart date:05/21/2012
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:0.9.1
Keywords: Affected PuppetDB version:
Branch:

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

This is on puppetdb-0.9.0-1.el5 with a centos 5 master running PE 2.5.0

I had a puppetdb.conf file that looked like this:

[main]
  server = puppetmaster.puppetlabs.vm
  port   = 8081

And Puppet gave me this error:

err: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit 'replace facts' command for puppetmaster.puppetlabs.vm to PuppetDB at puppetmaster.puppetlabs.vm
  port   = 8081:8080: getaddrinfo: Name or service not known
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run

It appears as if it thought the server for PuppetDB was “puppetmaster.puppetlabs.vm\n port = 8081” Killing the 2-space indent made things work!

History

#1 Updated by Deepak Giridharagopal almost 2 years ago

  • Status changed from Unreviewed to Accepted
  • Target version set to 0.9.1

Damn you, Puppet’s .conf parser!

#2 Updated by Deepak Giridharagopal almost 2 years ago

  • Status changed from Accepted to Merged - Pending Release

#3 Updated by Gary Larizza almost 2 years ago

Oh wow. Rock on, you guys! You should totally work for Pup-…oh. Nevermind.

#4 Updated by Matthaus Owens almost 2 years ago

Released in PuppetDB 0.9.1

#5 Updated by Matthaus Owens almost 2 years ago

  • Status changed from Merged - Pending Release to Closed

Also available in: Atom PDF