Project

General

Profile

Actions

Bug #3900

open

Class removed because invalid syntax validation

Added by Andrei Burd over 10 years ago. Updated over 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Puppet integration
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

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.


Related issues 6 (2 open4 closed)

Related to Foreman - Feature #7086: Puppet modules being skipped or failed to import should be reported or noticed by foreman.New08/14/2014Actions
Related to Foreman - Bug #11661: Puppet importer class should return a warning when a class is defined twiceNew09/02/2015Actions
Related to Smart Proxy - Feature #15095: Add Puppet server environment_classes API supportClosedActions
Related to Smart Proxy - Bug #2289: smart-proxy should warn when it cannot read some puppet module file or directoryResolved03/07/2013Actions
Has duplicate Foreman - Bug #9052: Foreman/foreman-proxy don't report classes skipped due to syntax error during import from Puppet.Duplicate01/20/2015Actions
Has duplicate Foreman - Feature #11393: Class importer should present useful errorsDuplicate08/17/2015Actions
Actions #1

Updated by Dominic Cleal over 10 years ago

  • Category set to Puppet integration
  • translation missing: en.field_release deleted (1)
Actions #2

Updated by Dominic Cleal over 9 years ago

  • Related to Feature #7086: Puppet modules being skipped or failed to import should be reported or noticed by foreman. added
Actions #3

Updated by Dominic Cleal about 9 years ago

  • Has duplicate Bug #9052: Foreman/foreman-proxy don't report classes skipped due to syntax error during import from Puppet. added
Actions #4

Updated by Dominic Cleal over 8 years ago

  • Has duplicate Feature #11393: Class importer should present useful errors added
Actions #5

Updated by Dominic Cleal over 8 years ago

  • Related to Bug #11661: Puppet importer class should return a warning when a class is defined twice added
Actions #6

Updated by Dominic Cleal almost 8 years ago

  • Related to Feature #15095: Add Puppet server environment_classes API support added
Actions #7

Updated by Dominic Cleal almost 8 years ago

  • Related to Bug #2289: smart-proxy should warn when it cannot read some puppet module file or directory added
Actions #8

Updated by Dominic Cleal over 7 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.

Actions

Also available in: Atom PDF