Bug #2111
Puppet goes into an infinite recursion with a host and resources { purge => true }
| Status: | Closed | Start date: | 03/26/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | plumbing | |||
| Target version: | 0.25.0 | |||
| Affected Puppet version: | 0.25.0 | Branch: | ||
| Keywords: | ||||
| Votes: | 0 |
Description
Here’s the test case:
$ puppet --trace test.pp
--- test.pp
node default {
host { "test":
ip => "1.2.3.4",
target => "/path/to/a/nondefault/hosts"
}
}
resources { host:
purge => true
}
---
I have no idea what’s going on here… but methinks it’s a bug…
History
Updated by Eric Gerlach about 3 years ago
- Subject changed from Puppet goes into an infinite recursion with a host with a non-default target and resources { purge => true } to Puppet goes into an infinite recursion with a host and resources { purge => true }
Did another test. The non-default target isn’t required. Remove the “target => ” line and the same thing occurs. New test case:
—– test.pp node default {
host { "test":
ip => "1.2.3.4"
}
}
resources { host:
purge => true
}¶
Updated by Luke Kanies about 3 years ago
- Category set to plumbing
- Status changed from Unreviewed to Accepted
- Assignee set to Luke Kanies
- Target version set to 0.25.0
Updated by Luke Kanies about 3 years ago
- Status changed from Accepted to Ready For Checkin
- Assignee changed from Luke Kanies to James Turnbull
Fixed in the tickets/master/2111 branch in my repo.
This was a doozie – probably the hardest bug I’ve tracked down in a year.
Updated by Luke Kanies about 3 years ago
- Status changed from Ready For Checkin to Closed
Merged as commit:88ff9c6500e76fdda02e60262dd1571577c0b92b.