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

Unable to create a service from a template #11071

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

Originally created by @jeremystretch on GitHub (Apr 23, 2025).

Originally assigned to: @jeremystretch on GitHub.

Deployment Type

Self-hosted

NetBox Version

v4.2.8

Python Version

3.10

Steps to Reproduce

  1. Create a device with at least one interface.
  2. Assign an IP address to an interface on the device.
  3. Create a service template for e.g. TCP/443.
  4. Click "add a service" under the device view. This will present the service creation form with the current device already selected.
  5. Select the service template and IP address, then click "create."

Expected Behavior

The service should be created.

Observed Behavior

No action is taken. The form does not appear to be submitted.

Originally created by @jeremystretch on GitHub (Apr 23, 2025). Originally assigned to: @jeremystretch on GitHub. ### Deployment Type Self-hosted ### NetBox Version v4.2.8 ### Python Version 3.10 ### Steps to Reproduce 1. Create a device with at least one interface. 2. Assign an IP address to an interface on the device. 3. Create a service template for e.g. TCP/443. 4. Click "add a service" under the device view. This will present the service creation form with the current device already selected. 5. Select the service template and IP address, then click "create." ### Expected Behavior The service should be created. ### Observed Behavior No action is taken. The form does not appear to be submitted.
adam added the type: bugstatus: acceptedseverity: medium labels 2025-12-29 21:39:51 +01:00
adam closed this issue 2025-12-29 21:39:51 +01:00
adam commented 2025-12-29 21:39:52 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 23, 2025):

It looks like the widget for the protocol field is rendered with the required attribute set, even though the field itself is not required. This appears to be a regression introduced by #18971, however we'll need to determine the proper fix as we definitely want to include the required attribute on <select> widgets where applicable.

@jeremystretch commented on GitHub (Apr 23, 2025): It looks like the widget for the `protocol` field is rendered with the `required` attribute set, even though the field itself is not required. This appears to be a regression introduced by #18971, however we'll need to determine the proper fix as we definitely want to include the `required` attribute on `<select>` widgets where applicable.
adam commented 2025-12-29 21:39:52 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 23, 2025):

As a workaround, you can select a protocol under the "Custom" tab. This will be ignored when a template is selected, and will allow the form to be submitted.

@jeremystretch commented on GitHub (Apr 23, 2025): As a workaround, you can select a protocol under the "Custom" tab. This will be ignored when a template is selected, and will allow the form to be submitted.
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#11071
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?