Bug #9491

--genconfig creating invalid configuration

Added by Chris Blumentritt 5 months ago. Updated 3 months ago.

Status:Accepted Start date:09/14/2011
Priority:Urgent Due date:
Assignee:- % Done:

0%
Category:executables
Target version:2.7.x
Affected Puppet version:2.7.3 Branch:
Keywords:genconfig
factdest
Votes: 0

Description

Puppet 2.7.3 using passenger

(/File[/var/lib/puppet/facts]) Not removing directory; use 'force' to override
(/File[/var/lib/puppet/facts]) Not removing directory; use 'force' to override
(/File[/var/lib/puppet/facts]/ensure) change from directory to file failed: Could not set 'file on ensure: Is a directory - /var/lib/puppet/facts

Commenting out

factdest = /var/lib/puppet/facts/ in /etc/puppet/puppet.conf

or

factsource = puppet://puppet/facts/

or both allows the puppet master to start.

puppet.conf (37.3 kB) Chris Blumentritt, 09/19/2011 08:10 am

Related issues

duplicated by Puppet - Bug #10991: puppet agent --genconfig generates unusable config Duplicate 11/21/2011

History

#1
Updated by James Turnbull 5 months ago

  • Status changed from Unreviewed to Needs More Information

Chris – what are you using for factdest and factsource for?

#2
Updated by Chris Blumentritt 5 months ago

I am not using anything. When I comment one of them out I guess it uses what ever is default. The following is a snippet from puppet.conf which would allow puppet to be started (note I am using passenger):

# Where Puppet should store facts that it pulls down from the central    # server.
# The default value is '$vardir/facts/'.
# factdest = /var/lib/puppet/facts/


# From where to retrieve facts.  The standard Puppet `file` type    # is used for retrieval, so anything that is a valid file source can    # be used here.
# The default value is 'puppet://$server/facts/'.
factsource = puppet://puppet/facts/

It might be just a conflict when running as a puppet master

#3
Updated by James Turnbull 5 months ago

Chris – neither of these options is really used anymore. You can safely comment out/delete both. I suspect the puppet.conf with your distro’s package is perhaps out of date?

#4
Updated by James Turnbull 5 months ago

Sorry missed the —genconfig in the title. There must be a recent regression.

#5
Updated by James Turnbull 5 months ago

  • Subject changed from factdest in puppet master --genconfig to --genconfig creating invalid configuration
  • Description updated (diff)
  • Status changed from Needs More Information to Needs Decision
  • Assignee set to Nigel Kersten

#6
Updated by Nigel Kersten 5 months ago

This is even more strange.

Do you have “factsync” enabled? Those options should be entirely inert unless factsync is set.

#7
Updated by Chris Blumentritt 5 months ago

factsync = false is commented out. I think the default is false. I have attached to config file

#8
Updated by Nigel Kersten 5 months ago

  • Status changed from Needs Decision to Accepted
  • Assignee deleted (Nigel Kersten)
  • Target version set to 2.7.x

#9
Updated by Nigel Kersten 3 months ago

  • Priority changed from Normal to Urgent

Also available in: Atom PDF