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

Script Server can raise unexpected warnings when 'arg_num_indexes' set but not found in data source #2974

Closed
cigamit opened this issue Sep 25, 2019 · 0 comments
Labels
bug Undesired behaviour resolved A fixed issue
Milestone

Comments

@cigamit
Copy link
Member

cigamit commented Sep 25, 2019

Describe the bug
If you have a Script Server Data Query that attempts to implement arg_num_indexes, even though that query will return no rows, cacti does not attempt to emulate using the index count returned by the index query, but instead fails.

To Reproduce
Steps to reproduce the behavior:

  1. Install the Mikrotik Plugin
  2. Discover a Mikrotik device
  3. Notice that the Mikrotik - Interfaces data query has zero rows

Expected behavior
Even though the 'arg_num_indexes' is defined in the XML file, we should not fail if it's unable to find any indexes.

@cigamit cigamit added bug Undesired behaviour resolved A fixed issue labels Sep 25, 2019
cigamit added a commit that referenced this issue Sep 25, 2019
Data Query Issue with Script Server when 'arg_num_indexes' set but not found
@cigamit cigamit added this to the v1.2.7 milestone Sep 25, 2019
@cigamit cigamit closed this as completed Sep 25, 2019
@netniV netniV changed the title Data Query Issue with Script Server when 'arg_num_indexes' set but not found Script Server can raise unexpected warnings when 'arg_num_indexes' set but not found in data source Sep 28, 2019
@github-actions github-actions bot locked and limited conversation to collaborators Jun 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Undesired behaviour resolved A fixed issue
Projects
None yet
Development

No branches or pull requests

1 participant