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 Rest API has no results #13061
Comments
Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports. |
I hope it is detailed enough. |
This fixed the GUI but not the Rest API I made bug about. Should I create a new bug report or do you want to reopen this one? Regards and many thanks for Netbox Marius |
That's right. There are still inconsistencies in calling |
@jiuka Please open a new bug report with a reference to this issue as this has been merged into a release. @cholyoak you could chime in that other issue should your comment be relevant to that issue as well. |
NetBox version
v3.5.4
Python version
3.11
Steps to Reproduce
bug.py
bug.py
file.Run Script
Expected Behavior
The
result
should be job result like in the reports endpoint.Observed Behavior
It is always
null
.The job.name is just the name of the script class. When search for the result the script.name
is used and not the
class_name
therefore no results are found, unless thename
ist set to the same value as theclass_name
.The text was updated successfully, but these errors were encountered: