-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configuration is deceptive on pdbtool(1)
error
#42
Comments
smortex
added a commit
that referenced
this issue
Aug 10, 2023
If a pattern database is failing, it is not installed, but on subsequent run of Puppet the pattern database is not tested again and the configuration to a state where the expected pattern database is not installed. Rework the pattern database testing and installation so that a failling pattern database fail on each subsequent run of Puppet, so that errors can be spotted more easily. Fixes #42
smortex
added a commit
that referenced
this issue
Aug 10, 2023
If a pattern database is failing, it is not installed, but on subsequent run of Puppet the pattern database is not tested again and the configuration converge to a state where the expected pattern database is not installed. Rework the pattern database testing and installation so that a failling pattern database fail on each subsequent run of Puppet, so that errors can be spotted more easily. Fixes #42
smortex
added a commit
that referenced
this issue
Aug 10, 2023
If a pattern database is failing, it is not installed, but on subsequent run of Puppet the pattern database is not tested again and the configuration converge to a state where the expected pattern database is not installed. Rework the pattern database testing and installation so that a failling pattern database fail on each subsequent run of Puppet, so that errors can be spotted more easily. Fixes #42
smortex
added a commit
that referenced
this issue
Aug 10, 2023
If a pattern database is failing, it is not installed, but on subsequent run of Puppet the pattern database is not tested again and the configuration converge to a state where the expected pattern database is not installed. Rework the pattern database testing and installation so that a failling pattern database fail on each subsequent run of Puppet, so that errors can be spotted more easily. Fixes #42
smortex
added a commit
that referenced
this issue
Aug 10, 2023
If a pattern database is failing, it is not installed, but on subsequent run of Puppet the pattern database is not tested again and the configuration converge to a state where the expected pattern database is not installed. Rework the pattern database testing and installation so that a failling pattern database fail on each subsequent run of Puppet, so that errors can be spotted more easily. Fixes #42
smortex
added a commit
that referenced
this issue
Aug 10, 2023
If a pattern database is failing, it is not installed, but on subsequent run of Puppet the pattern database is not tested again and the configuration converge to a state where the expected pattern database is not installed. Rework the pattern database testing and installation so that a failling pattern database fail on each subsequent run of Puppet, so that errors can be spotted more easily. Fixes #42
smortex
added a commit
that referenced
this issue
Aug 11, 2023
If a pattern database is failing, it is not installed, but on subsequent run of Puppet the pattern database is not tested again and the configuration converge to a state where the expected pattern database is not installed. Rework the pattern database testing and installation so that a failling pattern database fail on each subsequent run of Puppet, so that errors can be spotted more easily. Fixes #42
smortex
added a commit
that referenced
this issue
Aug 11, 2023
If a pattern database is failing, it is not installed, but on subsequent run of Puppet the pattern database is not tested again and the configuration converge to a state where the expected pattern database is not installed. Rework the pattern database testing and installation so that a failling pattern database fail on each subsequent run of Puppet, so that errors can be spotted more easily. Fixes #42
smortex
added a commit
that referenced
this issue
Aug 31, 2023
If a pattern database is failing, it is not installed, but on subsequent run of Puppet the pattern database is not tested again and the configuration converge to a state where the expected pattern database is not installed. Rework the pattern database testing and installation so that a failling pattern database fail on each subsequent run of Puppet, so that errors can be spotted more easily. Fixes #42
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When patterndb rules are changed:
/etc/syslog-ng/patterndb.d
;pdbtool(1)
is run to validate the merged rules and on success;/var/lib/syslog-ng/patterndb
.If at step 3 the command fail, the merged rules are not installed, and the user is reported by puppet.
But on the next run, the files in
/etc/syslog-ng/patterndb.d
match what is expected, no merge is done, no validation is tried, no installation is done. So we end-up with a catalog that apply successfully without changes, but we are still using the previous patterndb configuration.When adding broken rules, the process should fail at each puppet run until fixed.
The text was updated successfully, but these errors were encountered: