-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Can't Fully Remove Reports #2892
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
Comments
Also hitting this issue. Would like to be able to clean up the reports from the "Reports" box on the homepage. |
Tertiary confirmation. Ran into this recently, and with report renames the issue is ever present on the Netbox landing page. |
As a workaround fix you can delete the old/invalid report results in the |
Hitting same issue as well. Restart of Netbox doesn't work either.
As stated, it is only a workaround. A fix would be appreciated! Edit: it seems that restarting Netbox doesn't change anything. I guess the table in database is checked periodically for updating the UI, so wait for a while and you shouldn't see reports on the homepage anymore. |
You don't see the Changes in the UI, because they are cached in redis. |
Environment
Postgres: version 10.6
OS: Ubuntu 18.04.1 LTS
Steps to Reproduce
2.1 alternatively, remove the whole reports/ .py file
4.1 Homepage, "Reports" box still lists the missing report. Following the link gives a "page not found"
Expected Behavior
When I remove a "class" entry or the entire reports file, I would expect the corresponding link off the home page in the "reports" box to disappear, similar to "organization" -> "reports"
Observed Behavior
The link is still there. Following it gives a "page not found"
Suggestions from the peanut gallery / back-seat driver (me):
I can see not automatically deleting the report history/results just because the py file or the class is missing - that could protect me from myself on upgrades / editing reports.
Maybe a button under "Organization" -> "Reports" that does a "report cleanup" and removes reports from the database that don't exist anymore?
The text was updated successfully, but these errors were encountered: