You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the Cacti Graph API, if you encounter a Graph that has not Data Sources, it can not be removed using the standard API call.
To Reproduce
Steps to reproduce the behavior:
Create a Graph using a Template
Hack the Database to remove the Data Sources
Attempt to use the Cacti Graph API to remove the Graphs
Graphs will not be removed
Expected behavior
The Cacti API should recognize the "error" conditions and handle them properly. It's a corner case, but it can and does happen from time to time when a database has become damaged from a system crash during automation for example.
The text was updated successfully, but these errors were encountered:
netniV
changed the title
The Cacti API can not remove a Graph that has no Data Sources
When using API calls, a graph without sources mat be unremovable
Apr 3, 2022
netniV
changed the title
When using API calls, a graph without sources mat be unremovable
When using API calls, a graph without data sources may be unremovable
Apr 3, 2022
netniV
changed the title
When using API calls, a graph without data sources may be unremovable
When using API calls, graphs without data sources may be unremovable
Apr 3, 2022
Describe the bug
When using the Cacti Graph API, if you encounter a Graph that has not Data Sources, it can not be removed using the standard API call.
To Reproduce
Steps to reproduce the behavior:
Create a Graph using a Template
Hack the Database to remove the Data Sources
Attempt to use the Cacti Graph API to remove the Graphs
Graphs will not be removed
Expected behavior
The Cacti API should recognize the "error" conditions and handle them properly. It's a corner case, but it can and does happen from time to time when a database has become damaged from a system crash during automation for example.
The text was updated successfully, but these errors were encountered: