No error trace on reports #8915

New Issue

adam · 2025-12-29T20:42:49+01:00

adam commented

2025-12-29 20:42:49 +01:00

Originally created by @PaulR282 on GitHub (Dec 5, 2023).

NetBox version

v3.6.6

Python version

3.10

Steps to Reproduce

Add a report that crashes into the errored state

example:

from extras.reports import Report

class testtrace(Report):
    name = "testtrace"
    description = "testtrace"
    def test_trace(self):
        if true:
            raise NotImplementedError("Error")
        self.log_info(".",".")

Expected Behavior

A trace should be shown so you can troubleshoot the problem

Observed Behavior

Originally created by @PaulR282 on GitHub (Dec 5, 2023). ### NetBox version v3.6.6 ### Python version 3.10 ### Steps to Reproduce 1. Add a report that crashes into the `errored` state example: ``` from extras.reports import Report class testtrace(Report): name = "testtrace" description = "testtrace" def test_trace(self): if true: raise NotImplementedError("Error") self.log_info(".",".") ``` ### Expected Behavior A trace should be shown so you can troubleshoot the problem ### Observed Behavior ![image](https://github.com/netbox-community/netbox/assets/47193860/7619f672-14b3-4de6-ad24-fe591f3af72c)

adam added the type: bug label 2025-12-29 20:42:49 +01:00

adam closed this issue

2025-12-29 20:42:49 +01:00

adam commented

2025-12-29 20:42:50 +01:00

@jeremystretch commented on GitHub (Dec 5, 2023):

The report results list is intended to convey only information logged by reports directly, and not fatal errors. This would need to be a feature request, however #13334 has already been implemented for the upcoming release of NetBox v3.7. This change ensures that any errors resulting from the execution of a background job are recorded on the job record itself, which I believe satisfies your use case.

Also, take note that reports are slated for removal in NetBox v4.0 (see #12510).

@jeremystretch commented on GitHub (Dec 5, 2023): The report results list is intended to convey only information logged by reports directly, and not fatal errors. This would need to be a feature request, however #13334 has already been implemented for the upcoming release of NetBox v3.7. This change ensures that any errors resulting from the execution of a background job are recorded on the job record itself, which I believe satisfies your use case. Also, take note that reports are slated for removal in NetBox v4.0 (see #12510).

Sign in to join this conversation.

Branches Tags

main

update-changelog-comments-docs

feature-removal-issue-type

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#8915