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.

Sign up for GitHub

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

Jump to bottom

Exception for job details if object not set #17086

Closed
alehaa opened this issue Aug 6, 2024 · 2 comments
Closed

Exception for job details if object not set #17086

alehaa opened this issue Aug 6, 2024 · 2 comments
Assignees
@alehaa
Labels
beta Concerns a bug/feature in a beta release severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@alehaa
Copy link
Contributor

alehaa commented Aug 6, 2024

Deployment Type

Self-hosted

NetBox Version

v4.1-beta1

Python Version

3.11

Steps to Reproduce

  1. Create a new JobRunner.
  2. Schedule the job runner without an instance being passed to enqueue().
  3. Navigate to jobs view
  4. Open List item for newly created job

Expected Behavior

Job details are shown.

Observed Behavior

An exception is raised due to accessing _meta of the Job's object. However object is None as scheduled above.

This is due to 3028f26 introducing breadcrumbs for jobs. However, d6432fb introduced the job object being optional around the same time.
@alehaa alehaa added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Aug 6, 2024
@arthanson arthanson added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation and removed status: needs triage This issue is awaiting triage by a maintainer labels Aug 6, 2024
@arthanson arthanson removed their assignment Aug 6, 2024
@arthanson arthanson added the severity: low Does not significantly disrupt application functionality, or a workaround is available label Aug 6, 2024
@arthanson
Copy link
Collaborator

@alehaa do you want to take this one?

@alehaa
Copy link
Contributor Author

alehaa commented Aug 6, 2024 •
edited
Loading

@arthanson yep!

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Aug 6, 2024
@alehaa alehaa mentioned this issue Aug 7, 2024
Merged
@jeremystretch jeremystretch added the beta Concerns a bug/feature in a beta release label Aug 10, 2024
@jeremystretch jeremystretch mentioned this issue Sep 3, 2024
Merged
This was referenced Oct 6, 2024
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alehaa alehaa

Labels
beta Concerns a bug/feature in a beta release severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@arthanson @alehaa @jeremystretch