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 report does not run after netbox containers/pods restart #9687

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

Originally created by @winadm87 on GitHub (May 15, 2024).

Deployment Type

Self-hosted

NetBox Version

v3.6.4

Python Version

3.10

Steps to Reproduce

  1. Create a netbox report
  2. Schedule report to recurring for 5 min
  3. Wait for first schedule iteration, report will run and make a schedule for next run in next 5 min
  4. Restart netbox pods/containers, e.g. docker compose restart

Expected Behavior

Netbox pods/containers restart should not affect scheduled reports

Observed Behavior

Go back to UI and observe that scheduled job pass next iteration time without execution and do not re-schedule itself.
We can observe the same behavior as for "local docker compose deployment" and for k8s deployment.

Originally created by @winadm87 on GitHub (May 15, 2024). ### Deployment Type Self-hosted ### NetBox Version v3.6.4 ### Python Version 3.10 ### Steps to Reproduce 1. Create a netbox report 2. Schedule report to recurring for 5 min 3. Wait for first schedule iteration, report will run and make a schedule for next run in next 5 min 4. Restart netbox pods/containers, e.g. `docker compose restart` ### Expected Behavior Netbox pods/containers restart should not affect scheduled reports ### Observed Behavior Go back to UI and observe that scheduled job pass next iteration time without execution and do not re-schedule itself. We can observe the same behavior as for "local docker compose deployment" and for k8s deployment.
adam closed this issue 2025-12-29 21:20:51 +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#9687
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?