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

Custom scripts in symlinked path don't work #11261

New Issue
Closed
opened 2025-12-29 21:42:37 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:42:37 +01:00
Owner
Copy Link

Originally created by @llamafilm on GitHub (Jun 5, 2025).

Originally assigned to: @arthanson on GitHub.

Deployment Type

Self-hosted

NetBox Version

v4.3.1

Python Version

3.10

Steps to Reproduce

  1. Install Netbox 4.3.1, following the instructions to use a symlinked path /opt/netbox
  2. Create a custom script from the /extras/scripts/add webpage
  3. Run the script

Expected Behavior

it should work

Observed Behavior

Script fails with no error message shown.

When you enable debug level logging for netbox.data_backends it shows this:

netbox.data_backends[9596]: Failed to load script: connect_power error: The joined path (/opt/netbox/netbox/scripts/connect_power.py) is located outside of the base path component (/opt/netbox-4.3.1/netbox/scripts)

Image

I first saw this issue on my prod Netbox after upgrading to 4.3.1 and creating a new script. All my old scripts still work fine. I reproduced the issue on a fresh install. In this case, I didn't customize anything, just used all the defaults, including the recommendation for symlinking /opt/netbox.

Here is the difference between the new broken script and an older, working script on my prod instance:

netbox=> SELECT id,data_path,file_path,data_file_id,data_source_id,auto_sync_enabled FROM core_managedfile ORDER BY CREATED DESC LIMIT 2;
 id  |             data_path              |                  file_path                  | data_file_id | data_source_id | auto_sync_enabled 
-----+------------------------------------+---------------------------------------------+--------------+----------------+-------------------
 208 |                                    | /opt/netbox/netbox/scripts/connect_power.py |              |                | f
 206 | scripts/import_terrier_mactable.py | import_terrier_mactable.py                  |         7727 |             35 | t
Originally created by @llamafilm on GitHub (Jun 5, 2025). Originally assigned to: @arthanson on GitHub. ### Deployment Type Self-hosted ### NetBox Version v4.3.1 ### Python Version 3.10 ### Steps to Reproduce 1. Install Netbox 4.3.1, following the [instructions](https://netboxlabs.com/docs/netbox/installation/netbox/) to use a symlinked path `/opt/netbox` 2. Create a custom script from the `/extras/scripts/add` webpage 3. Run the script ### Expected Behavior it should work ### Observed Behavior Script fails with no error message shown. When you enable debug level logging for `netbox.data_backends` it shows this: > netbox.data_backends[9596]: Failed to load script: connect_power error: The joined path (/opt/netbox/netbox/scripts/connect_power.py) is located outside of the base path component (/opt/netbox-4.3.1/netbox/scripts) ![Image](https://github.com/user-attachments/assets/936ca0b7-aae8-4132-a989-77f715fe62df) I first saw this issue on my prod Netbox after upgrading to 4.3.1 and creating a new script. All my old scripts still work fine. I reproduced the issue on a fresh install. In this case, I didn't customize anything, just used all the defaults, including the recommendation for symlinking `/opt/netbox`. Here is the difference between the new broken script and an older, working script on my prod instance: ``` netbox=> SELECT id,data_path,file_path,data_file_id,data_source_id,auto_sync_enabled FROM core_managedfile ORDER BY CREATED DESC LIMIT 2; id | data_path | file_path | data_file_id | data_source_id | auto_sync_enabled -----+------------------------------------+---------------------------------------------+--------------+----------------+------------------- 208 | | /opt/netbox/netbox/scripts/connect_power.py | | | f 206 | scripts/import_terrier_mactable.py | import_terrier_mactable.py | 7727 | 35 | t ```
adam added the type: bugstatus: acceptedseverity: medium labels 2025-12-29 21:42:37 +01:00
adam closed this issue 2025-12-29 21:42:38 +01:00
adam commented 2025-12-29 21:42:38 +01:00
Author
Owner
Copy Link

@llamafilm commented on GitHub (Jun 5, 2025):

I was able to workaround this by just changing the file_path. I left data_path blank, I'm not sure if that matters.

UPDATE core_managedfile SET file_path = 'connect_power.py' WHERE id = 208;
@llamafilm commented on GitHub (Jun 5, 2025): I was able to workaround this by just changing the file_path. I left data_path blank, I'm not sure if that matters. ```sql UPDATE core_managedfile SET file_path = 'connect_power.py' WHERE id = 208; ```
adam commented 2025-12-29 21:42:39 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Jun 13, 2025):

This should be fixed by #19698

@arthanson commented on GitHub (Jun 13, 2025): This should be fixed by #19698
adam commented 2025-12-29 21:42:39 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Jun 13, 2025):

I'm going to go ahead and close this as a duplicate, as Arthur references. If it turns out to be a separate issue, we can re-open.

@jnovinger commented on GitHub (Jun 13, 2025): I'm going to go ahead and close this as a duplicate, as Arthur references. If it turns out to be a separate issue, we can re-open.
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 severity: medium 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#11261
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?