Bug #638
Puppet complains about incorrect mode/owner/group on nonexistant files in noop mode, but not otherwise
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | - | |||
| Target version: | - | |||
| Affected Puppet version: | 0.25.4 | Branch: | ||
| Keywords: | ||||
| Votes: | 0 |
Description
When you are only setting mode/owner/group on a nonexistant file, puppet will complain about them being wrong when running in noop mode, however, when running normally it will not complain or update anything or create the file. The bug is that noop mode is reporting actions that puppet will not actually take if run in normal update mode.
Personally I think the behavior of the normal run mode is correct (to ignore the file unless it exists).
Example:
% cat test.pp
file { "/tmp/test":
owner => root,
group => root,
mode => 0644,
}
% ls -l /tmp/test
ls: /tmp/test: No such file or directory
% sudo puppet --noop test.pp
Password:
notice: //File[/tmp/test]/owner: is absent, should be root (noop)
notice: //File[/tmp/test]/group: is absent, should be root (noop)
notice: //File[/tmp/test]/mode: is absent, should be 644 (noop)
% sudo puppet test.pp
% ls -l /tmp/test
ls: /tmp/test: No such file or directory
History
Updated by Luke Kanies about 5 years ago
- Status changed from 1 to Closed
- 7 set to worksforme
This was fixed in 0.22.4, revision r2371.