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 deleting a single Data Source, purge historical debug data #5534

Closed
TheWitness opened this issue Oct 14, 2023 · 0 comments
Closed

When deleting a single Data Source, purge historical debug data #5534

TheWitness opened this issue Oct 14, 2023 · 0 comments
Labels
bug Undesired behaviour confirmed Bug is confirm by dev team resolved A fixed issue
Milestone

Comments

@TheWitness
Copy link
Member

Describe the bug

Ran across this one today. When removing a single Data Source, the table data_debug is not handled.

To Reproduce

Steps to reproduce the behavior:

  1. Start a Data Debug Run
  2. Before it starts Remove Data Sources using the function api_data_source_remove_multi()
  3. Wait for the Data Source debug run to complete
  4. Watch the Cacti Log and the number of checks to perform never goes down.

Expected behavior

Cacti should remove these entries.

@TheWitness TheWitness added bug Undesired behaviour confirmed Bug is confirm by dev team labels Oct 14, 2023
@TheWitness TheWitness added this to the 1.2.26 milestone Oct 14, 2023
@TheWitness TheWitness added the resolved A fixed issue label Oct 14, 2023
TheWitness added a commit that referenced this issue Oct 14, 2023
When deleting a single Data Source the table data_debug is not purged
TheWitness added a commit that referenced this issue Oct 14, 2023
When deleting a single Data Source the table data_debug is not purged
@netniV netniV changed the title When deleting a single Data Source the table data_debug is not purged When deleting a single Data Source, purge historical debug data Dec 16, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Mar 16, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Undesired behaviour confirmed Bug is confirm by dev team resolved A fixed issue
Projects
None yet
Development

No branches or pull requests

1 participant