Bug #7495
Downgrade error about pluginsync failures due to non-existent/empty plugins source to info line
| Status: | Accepted | Start date: | 05/11/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | 2.7.x | |||
| Affected Puppet version: | Branch: | |||
| Keywords: | ||||
| Votes: | 1 |
Description
This is a very confusing error for users, we’re going to satisfy the most common case (pluginsync is on, no modules in modulepath have a lib/ subdirectory) and just print it as an info line.
Something like:
info: Pluginsync on, but pluginsource empty or non-existent. perhaps? Feedback on info line welcome.
History
Updated by Nick Fagerlund about 1 year ago
The part that worries me is that you only know what pluginsource is if you’ve tweaked with it; by default, it’s completely ephemeral and nameless, and is distributed across god only knows how many modules. I’d say just Pluginsync on, but no plugins found would be less confusing.