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

If a DataSource sync fails (for example RQ timeout), the DataSource will be stuck as un-syncable. #7597

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

Originally created by @kkthxbye-code on GitHub (Feb 3, 2023).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.5.0-dev

Python version

3.10

Steps to Reproduce

Sorry for the iffy replication steps, I ran into this while debugging rqworker which made the job timeout.

  1. Create a DataSouce pointing to a local directory
  2. Create a file in the local directory
  3. Sync the DataSource
  4. Make sure the job doesn't finish within the configured RQ_DEFAULT_TIMEOUT (for example by debugging)

Expected Behavior

The DataSource should be syncable still.

Observed Behavior

The status of the DataSource is stuck at syncing causing the sync button to be greyed out.

Originally created by @kkthxbye-code on GitHub (Feb 3, 2023). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.5.0-dev ### Python version 3.10 ### Steps to Reproduce Sorry for the iffy replication steps, I ran into this while debugging rqworker which made the job timeout. 1. Create a DataSouce pointing to a local directory 2. Create a file in the local directory 3. Sync the DataSource 4. Make sure the job doesn't finish within the configured RQ_DEFAULT_TIMEOUT (for example by debugging) ### Expected Behavior The DataSource should be syncable still. ### Observed Behavior The status of the DataSource is stuck at `syncing` causing the sync button to be greyed out.
adam added the type: bugstatus: acceptedbeta labels 2025-12-29 20:25:53 +01:00
adam closed this issue 2025-12-29 20:25:53 +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 beta status: accepted type: bug
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#7597
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?