Bug #4378
standalone Puppet 0.25.5 does not sync module Facts
| Status: | Needs More Information | Start date: | 07/27/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Affected Puppet version: | 0.25.5 | Branch: | ||
| Keywords: | modules standalone facter | |||
| Votes: | 0 |
Description
I’ve had a lot of success in using standalone Puppet (0.25.5 from EPEL) to bootstrap servers without the need for a puppetmaster.
But the ‘puppet’ executable cannot see facts that are defined under modules. I’ve tried various settings (—pluginsync —factpath /var/lib/puppet/lib/facter) to try to encourage it, but nothing works.
The workaround is to point puppet directly at the fact directory (with —factpath /bootstrap/modules/foo/lib/facter) – which works, but obviously only for one module.
Custom types and providers seem to work correctly (I am using camptocamps mysql module).
I’ve cut a miniwal config that shows the problem (attached, see the 2 shell scripts for full details).
History
Updated by James Turnbull over 1 year ago
- Status changed from Unreviewed to Needs More Information
Dick -any chance you could try 2.6.0 and see if this is fixed?
Updated by Dick Davies over 1 year ago
Yes, it works in 2.6.0 (testing on a Mac, the bug was filed on what’s in 0.25.5).