Puppet: System Administration Automated

Support

Ticket #1230 (closed defect: duplicate)

Opened 3 months ago

Last modified 3 months ago

facts not (always) set in a puppet run

Reported by: do Assigned to: luke
Priority: normal Milestone:
Component: unknown Version: 0.24.4
Severity: normal Keywords: facter, debian, darwin
Cc: Triage Stage: Needs more info
Attached Patches: None Complexity: Unknown

Description

Some facts are not set when puppet runs. Both server and client are 0.24.4(-6 on debian).

When I restart the server everything works well for some time. When I run facter on the command line all facts are set as they should.

After the server runs for some time, some facts are not set any more. This happens only with some facts. $processor in my case.

Operating systems are: Mac OS X and Debian Etch

Change History

05/20/08 00:56:11 changed by jamtur01

  • stage changed from Unreviewed to Needs more info.

Can you give some more precise explanation of what you mean by "not set"? Also logs, traces and the like? Thanks!

05/20/08 03:10:56 changed by luke

  • status changed from new to closed.
  • resolution set to duplicate.

I can just about guarantee you that this is a result of #1228, so I'm closing this as a duplicate based on that assumption. Please reopen it if that's not true.

Basically, your facts are getting cached in the yamldir/facts under a different name than the node cache in yamldir/node, which is causing the node not to be able to find the facts.

05/20/08 09:02:56 changed by do

are you sure it is #1228 (Create RSpec tests for lib/puppet/util/storage.rb) ? sound strange to me...

05/20/08 10:44:37 changed by jamtur01

I think he means either or both of #1147 and #1178

05/20/08 16:23:35 changed by luke

Sorry, yeah, it's #1178.