starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Cannot view reports after upgrade to 2.4.0 #1904

New Issue
Closed
opened 2025-12-29 17:20:15 +01:00 by adam · 4 comments
adam commented 2025-12-29 17:20:15 +01:00
Owner
Copy Link

Originally created by @SA0TAY on GitHub (Aug 7, 2018).

Environment

  • Python version: 3.5.3
  • NetBox version: 2.4

Steps to Reproduce

  • Run a report from the command line with manage.py runreport. Note the apparent success:
[12:41:37] Running device.BackupStatus...
	test_backup_config: 689 success, 0 info, 89 warning, 0 failure
	test_backup_status: 689 success, 0 info, 146 warning, 0 failure
	test_backup_success: 256 success, 0 info, 2 warning, 0 failure
[12:42:09] device.BackupStatus: SUCCESS
[12:42:09] Finished
  • Navigate to the Reports view in the web interface. The timestamp and the results overview in the right-hand column match with the returned output from the previous command.
  • Click on the report in question to read it.

Expected Behavior

The report, having been successfully run and acknowledged as such in the prior view, should open and show the details.

Observed Behavior

A page with the words No results are available for this report. Please run the report first. appear.

This bug is distinct from #2312 in that I can run reports but not view them, whereas the other reporter can view reports but not run them.

Originally created by @SA0TAY on GitHub (Aug 7, 2018). <!-- NOTE: This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.5.3 * NetBox version: 2.4 <!-- Describe in detail the steps that someone else can take to reproduce this bug using the current stable release of NetBox (or the current beta release where applicable). --> ### Steps to Reproduce * Run a report from the command line with manage.py runreport. Note the apparent success: ``` [12:41:37] Running device.BackupStatus... test_backup_config: 689 success, 0 info, 89 warning, 0 failure test_backup_status: 689 success, 0 info, 146 warning, 0 failure test_backup_success: 256 success, 0 info, 2 warning, 0 failure [12:42:09] device.BackupStatus: SUCCESS [12:42:09] Finished ``` * Navigate to the Reports view in the web interface. The timestamp and the results overview in the right-hand column match with the returned output from the previous command. * Click on the report in question to read it. <!-- What did you expect to happen? --> ### Expected Behavior The report, having been successfully run and acknowledged as such in the prior view, should open and show the details. <!-- What happened instead? --> ### Observed Behavior A page with the words `No results are available for this report. Please run the report first.` appear. This bug is distinct from #2312 in that I can run reports but not view them, whereas the other reporter can view reports but not run them.
adam closed this issue 2025-12-29 17:20:15 +01:00
adam commented 2025-12-29 17:20:16 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 7, 2018):

What is your REPORTS_ROOT setting (in configuration.py)?

@jeremystretch commented on GitHub (Aug 7, 2018): What is your `REPORTS_ROOT` setting (in `configuration.py`)?
adam commented 2025-12-29 17:20:16 +01:00
Author
Owner
Copy Link

@SA0TAY commented on GitHub (Aug 7, 2018):

No variable by that name is set in that file.

@SA0TAY commented on GitHub (Aug 7, 2018): No variable by that name is set in that file.
adam commented 2025-12-29 17:20:16 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 7, 2018):

#2312 should be fixed now and it's very likely this is related. Can you please try v2.4.1 and see if you still have this issue?

Edit: Also, what version of Python are you running?

@jeremystretch commented on GitHub (Aug 7, 2018): #2312 should be fixed now and it's very likely this is related. Can you please try v2.4.1 and see if you still have this issue? Edit: Also, what version of Python are you running?
adam commented 2025-12-29 17:20:16 +01:00
Author
Owner
Copy Link

@SA0TAY commented on GitHub (Aug 7, 2018):

Thank you, it works!

(Re edit: 3.5.3, as per the original post.)

@SA0TAY commented on GitHub (Aug 7, 2018): Thank you, it works! (Re edit: 3.5.3, as per the original post.)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#1904
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?