-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Custom Script Scheduling Broken #17921
Labels
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
wz4
added
status: needs triage
This issue is awaiting triage by a maintainer
type: bug
A confirmed report of unexpected behavior in the application
labels
Nov 2, 2024
arthanson
added
status: accepted
This issue has been accepted for implementation
severity: low
Does not significantly disrupt application functionality, or a workaround is available
and removed
status: needs triage
This issue is awaiting triage by a maintainer
labels
Nov 4, 2024
@alehaa can you comment on this and I can assign your. |
arthanson
added
status: needs owner
This issue is tentatively accepted pending a volunteer committed to its implementation
and removed
status: accepted
This issue has been accepted for implementation
labels
Nov 4, 2024
I can take a look at it. |
I believe this is related to #17923, as I get this error on the worker console:
After applying the patch for #17923 jobs will be scheduled as expected again. |
arthanson
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
Nov 5, 2024
jeremystretch
pushed a commit
that referenced
this issue
Nov 21, 2024
…17932) * Fix non-null constraint for script execution With c34a0e2, validation of job object fields is enabled, so ScriptJob must not set required fields to empty strings. This commit reverts b18f193 and (hopefully) fixes this issue not only for UI views, but for all interactions with scripts. Fixes: #17923 * Fix name of recurring jobs For recurring jobs, the name must be passed to the next job object when the job is rescheduled.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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
Deployment Type
Self-hosted
Triage priority
N/A
NetBox Version
v4.1.6
Python Version
3.10
Steps to Reproduce
In Netbox v4.1.6 schedule a recurring custom script. The first job will get scheduled, but subsequent jobs are not.
Test Script
Expected Behavior
After a scheduled job completes, the next scheduled job should appear with a status of 'Scheduled'.
Observed Behavior
No observed error
The text was updated successfully, but these errors were encountered: