Bug #966
Multiple Class definitons not detected
| 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
Up until 0.24 we had “class proxy” defined multiple times in our manifests. Infact one class actually included the other proxy so it would have created:
class proxy {
include proxy
}
Somehow this was working (just dumb luck I guess) until 0.24. Perhaps there should be a check to make sure that classes aren’t defined multiple times or at least a better error message here:
err: Could not apply complete catalog: Found cycles in the following relationships: Class[proxy] => Class[proxy]
I’m not sure if this error was from having multiple proxy classes defined or if it was because a class included itself.
History
Updated by Luke Kanies about 4 years ago
- Status changed from 1 to Closed
- 7 set to duplicate
This is basically a dup of #857, I think.