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

Scripts endpoint not working after v4.3.3 upgrade (from 4.2.6) #11379

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

Originally created by @stavr666 on GitHub (Jul 14, 2025).

Deployment Type

Self-hosted

NetBox Version

v4.3.3

Python Version

3.11

Steps to Reproduce

  1. Netbox v4.2.6 everyone use scripts for reporting and any complex tasks
  2. Netbox upgraded to v.4.3.3, without issues

Expected Behavior

Everything works as expected (except GQL, in line with "Breaking Changes").

Observed Behavior

Every other menu and functions works fine.

But https://<NETBOX_URL>/extras/scripts/ not working at all:
Image

No visible indicators found for source of issue (search gave me irrelevant cases).

P.S. Rebooted both Postgres and Netbox servers, upgrade.sh returning no errors. Gunicorn log contain no errors, except GraphQL syntax.

Originally created by @stavr666 on GitHub (Jul 14, 2025). ### Deployment Type Self-hosted ### NetBox Version v4.3.3 ### Python Version 3.11 ### Steps to Reproduce 1. Netbox v4.2.6 everyone use scripts for reporting and any complex tasks 2. Netbox upgraded to v.4.3.3, without issues ### Expected Behavior Everything works as expected (except GQL, in line with "Breaking Changes"). ### Observed Behavior Every other menu and functions works fine. But https://<NETBOX_URL>/extras/scripts/ not working at all: <img width="804" height="482" alt="Image" src="https://github.com/user-attachments/assets/933a7846-b8fd-485b-b11e-8ca4580ac0e3" /> No visible indicators found for source of issue (search gave me irrelevant cases). P.S. Rebooted both Postgres and Netbox servers, upgrade.sh returning no errors. Gunicorn log contain no errors, except GraphQL syntax.
adam added the type: bugstatus: duplicatetopic: scripts labels 2025-12-29 21:44:24 +01:00
adam closed this issue 2025-12-29 21:44:24 +01:00
adam commented 2025-12-29 21:44:25 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Jul 14, 2025):

@stavr666 , please take a look at https://github.com/netbox-community/netbox/issues/19045, which I think describes the same situation you are in. In that case, the reporter was using a reserved name (description) as a script variable, which will no longer work as of v4.2.7 and later. In particular, see my comment from April 15 in the thread for that issue.

@jnovinger commented on GitHub (Jul 14, 2025): @stavr666 , please take a look at https://github.com/netbox-community/netbox/issues/19045, which I think describes the same situation you are in. In that case, the reporter was using a reserved name (`description`) as a script variable, which will no longer work as of v4.2.7 and later. In particular, see my [comment from April 15](https://github.com/netbox-community/netbox/issues/19045#issuecomment-2805916624) in the thread for that issue.
adam commented 2025-12-29 21:44:25 +01:00
Author
Owner
Copy Link

@stavr666 commented on GitHub (Jul 15, 2025):

Yes, you're right, renaming variables fixed the issue. Thank you.
Only list not worked, btw, going to script by ID showed it correctly.

There must either fix this UI/api bug, or explicit way to know about new naming restrictions (in docs, in error code), without reading all comments in all "scripts"-related issues.

@stavr666 commented on GitHub (Jul 15, 2025): Yes, you're right, renaming variables fixed the issue. Thank you. Only list not worked, btw, going to script by ID showed it correctly. There must either fix this UI/api bug, or explicit way to know about new naming restrictions (in docs, in error code), without reading all comments in all "scripts"-related issues.
adam commented 2025-12-29 21:44:25 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Jul 31, 2025):

Closing as dupe of #19045

@arthanson commented on GitHub (Jul 31, 2025): Closing as dupe of #19045
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 status: duplicate topic: scripts 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#11379
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?