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

Scheduled Script are not persistent #10085

New Issue
Closed
opened 2025-12-29 21:26:43 +01:00 by adam · 0 comments
adam commented 2025-12-29 21:26:43 +01:00
Owner
Copy Link

Originally created by @dga-nagra on GitHub (Aug 13, 2024).

Deployment Type

NetBox Cloud

NetBox Version

v4.0.8

Python Version

3.11

Steps to Reproduce

  1. Create a netbox instance (on a VM, docker, ...) with external database & redis
  2. Schedule a script
  3. Delete the netbox instance (the whole VM/container/...)
  4. Recreate a new netbox instance

=> The scheduled script are not scheduled anymore
NOTE: This is a common way of working with containers /working with hashicorp packer to create an deploy a new image.

Expected Behavior

The scripts' scheduling should be persistent, i.e. still work as long as the database & redis are kept.

  • Apparently, the current system uses the crontab which is not ideal. It should rely on something else, like a redis feature
  • Schedules should be a new model so we can create/edit/delete them easily. On Netbox startup, it should check this table and ensure that the scheduling is configured correctly (whatever the method used)

Observed Behavior

After re-creating the instance, the script are not scheduled anymore.

Originally created by @dga-nagra on GitHub (Aug 13, 2024). ### Deployment Type NetBox Cloud ### NetBox Version v4.0.8 ### Python Version 3.11 ### Steps to Reproduce 1. Create a netbox instance (on a VM, docker, ...) with external database & redis 2. Schedule a script 3. Delete the netbox instance (the whole VM/container/...) 4. Recreate a new netbox instance => The scheduled script are not scheduled anymore NOTE: This is a common way of working with containers /working with hashicorp packer to create an deploy a new image. ### Expected Behavior The scripts' scheduling should be persistent, i.e. still work as long as the database & redis are kept. * Apparently, the current system uses the crontab which is not ideal. It should rely on something else, like a redis feature * Schedules should be a new model so we can create/edit/delete them easily. On Netbox startup, it should check this table and ensure that the scheduling is configured correctly (whatever the method used) ### Observed Behavior After re-creating the instance, the script are not scheduled anymore.
adam closed this issue 2025-12-29 21:26:43 +01:00
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#10085
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?