Bug #3900
open
Class removed because invalid syntax validation
Description
Hi!
I recently made the following change in the manifest:
nginx::server { 'repo':
listen_port => '7897',
- sname => "repo",
+ sname => "repo repo-${downcase(::location)}.rvzr.net",
docroot => '/var/repo'
}
That lead to deleting the class from the class as as I understood because of validation problems, but puppet applied everything ok.
and because of Bug #2394 it did delete class from one of the hosts that lead to produstion issues.
Updated by Dominic Cleal almost 11 years ago
- Category set to Puppet integration
- Translation missing: en.field_release deleted (
1)
Updated by Dominic Cleal over 10 years ago
- Related to Feature #7086: Puppet modules being skipped or failed to import should be reported or noticed by foreman. added
Updated by Dominic Cleal almost 10 years ago
- Has duplicate Bug #9052: Foreman/foreman-proxy don't report classes skipped due to syntax error during import from Puppet. added
Updated by Dominic Cleal over 9 years ago
- Has duplicate Feature #11393: Class importer should present useful errors added
Updated by Dominic Cleal about 9 years ago
- Related to Bug #11661: Puppet importer class should return a warning when a class is defined twice added
Updated by Dominic Cleal over 8 years ago
- Related to Feature #15095: Add Puppet server environment_classes API support added
Updated by Dominic Cleal over 8 years ago
- Related to Bug #2289: smart-proxy should warn when it cannot read some puppet module file or directory added
Updated by Dominic Cleal about 8 years ago
#15095 provides a smart proxy API with the error information, however #7086 should probably be implemented first to make use of it.
Implementing this may need some memorising of which class was imported from where, so when a syntax error occurs it can skip classes originally imported from the file with the error.