Feature #4093
manifest changes do not load immediately
| Status: | Closed | Start date: | 06/29/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | - | |||
| Target version: | 2.6.0 | |||
| Affected Puppet version: | 2.6alpha1 | Branch: | ||
| Keywords: | ||||
| Votes: | 0 |
Description
when I make changes to my site.pp file, they are not immediately reflected in the agents compiled catalog (in client/server mode)
site.pp
file { '/tmp/one':
ensure => directory,
}
site-broken.pp
file { '/tmpe/one':
ensure => directory,
}
from the broken to working site.pp, then it has some sync issues:
[root@puppet2 manifests]# puppetd -t warning: /User[puppet]: 'check' attribute is deprecated; use 'audit' instead info: Caching catalog for puppetclient info: Applying configuration version '1277475621' # we start out in the broken state err: //File[/tmpe/one]/ensure: change from absent to directory failed: Cannot create /tmpe/one; parent directory /tmpe does not exist notice: Finished catalog run in 0.03 seconds # here I change the site.pp to make it work again. [root@puppet2 manifests]# vi site.pp [root@puppet2 manifests]# puppetd -t warning: /User[puppet]: 'check' attribute is deprecated; use 'audit' instead info: Caching catalog for puppetclient info: Applying configuration version '1277475621' # it should work, but it doesnt. err: //File[/tmpe/one]/ensure: change from absent to directory failed: Cannot create /tmpe/one; parent directory /tmpe does not exist notice: Finished catalog run in 0.03 seconds # it works on the second time. [root@puppet2 manifests]# puppetd -t warning: /User[puppet]: 'check' attribute is deprecated; use 'audit' instead info: Caching catalog for puppetclient info: Applying configuration version '1277475637' notice: Finished catalog run in 0.02 seconds [root@puppet2 manifests]#
History
Updated by Dan Bode almost 2 years ago
- Subject changed from file changes do not load immediately to manifest changes do not load immediately
Updated by Alan Barrett almost 2 years ago
I would expect to have to wait up to ‘filetimeout’ seconds before the master notices a change.
Updated by Markus Roberts almost 2 years ago
- Status changed from Unreviewed to Needs More Information
- Assignee set to Dan Bode
Does adding the “—filetimeout 0” option give you the behavior you want?
Updated by Matt Robinson almost 2 years ago
- Target version set to 2.6.0
Updated by Dan Bode almost 2 years ago
as long as this is the expected behavior, I can handle it. Is this behavior change documented somewhere? (release notes?)
Updated by Markus Roberts almost 2 years ago
It’s not a behavior change AFAIK. If you are sure that it is, and I’m missing something, walk me through it.
Updated by James Turnbull almost 2 years ago
- Status changed from Needs More Information to Closed
Not a behaviour change – please re-open if you think it needs further exposition.