Skip to content
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

When format file does not exist, changing certain settings may result in errors #4645

Closed
TheWitness opened this issue Mar 23, 2022 · 0 comments
Labels
bug Undesired behaviour QA Bug created between releases. So, no CHANGELOG entry required resolved A fixed issue
Milestone

Comments

@TheWitness
Copy link
Member

Describe the bug

After a recent update to the Syslog plugin, it was found that there are cases where if you attempt to use Cacti's format file functions when the format file does not exist, Cacti will generate warnings.

To Reproduce

Steps to reproduce the behavior:

  1. Create a report that uses a standard cacti format file, then in the database, clear the format file. Make it blank.

  2. Generate the report

  3. Goto the Cacti log and see the errors.

Expected behavior

Cacti should use the default or return an error if the default is not present.

@TheWitness TheWitness added bug Undesired behaviour unverified Some days we don't have a clue and removed unverified Some days we don't have a clue labels Mar 23, 2022
@TheWitness TheWitness added this to the v1.2.20 milestone Mar 23, 2022
netniV pushed a commit that referenced this issue Mar 28, 2022
@TheWitness TheWitness added resolved A fixed issue QA Bug created between releases. So, no CHANGELOG entry required labels Mar 29, 2022
@netniV netniV changed the title If you attempt to use a format file for a non-existant setting Cacti throws warnings When format file does not exist, certain settings may result in errors Apr 3, 2022
@netniV netniV changed the title When format file does not exist, certain settings may result in errors When format file does not exist, changing certain settings may result in errors Apr 3, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Dec 1, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Undesired behaviour QA Bug created between releases. So, no CHANGELOG entry required resolved A fixed issue
Projects
None yet
Development

No branches or pull requests

1 participant