Bug #4222
Improve puppet error message for invalid options
| Status: | Accepted | Start date: | 07/13/2010 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | error reporting | |||
| Target version: | - | |||
| Affected Puppet version: | 2.6.0 | Branch: | ||
| Keywords: | ||||
| Votes: | 0 |
Description
When dealing with an invalid option, puppet should provide more meaningful error message:
$ puppet -verbose Could not parse for environment production: Syntax error at end of file at line 1
This should generate something along the line of “-verbose invalid option”.
History
Updated by Nan Liu over 1 year ago
- Priority changed from Normal to Low
Updated by James Turnbull over 1 year ago
- Category set to error reporting
- Status changed from Unreviewed to Needs More Information
- Assignee set to Nan Liu
Can you test this on 2.6.0? I think you’ll find it’s improved.
Updated by Nan Liu over 1 year ago
- Affected Puppet version changed from 0.25.5 to 2.6.0rc4
Testing on 2.6 rc4 shows same error message:
$ puppet —noop -verbose test.pp Could not parse for environment production: Syntax error at end of file at line 1 on node unknown.demo.lan
$ puppet —noop —verbose test.pp info: Applying configuration version ‘1278795864’ notice: /Stage[main]//Cron[cron1]/ensure: is absent, should be present (noop)
Updated by Nan Liu over 1 year ago
- Status changed from Needs More Information to Unreviewed
- Assignee changed from Nan Liu to James Turnbull
Updated by James Turnbull over 1 year ago
- Status changed from Unreviewed to Accepted
- Assignee deleted (
James Turnbull) - Target version set to 52
- Affected Puppet version changed from 2.6.0rc4 to 2.6.0
Updated by James Turnbull 11 months ago
- Target version deleted (
52)