Skip to content

Unable to create a service from a template #19281

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jeremystretch opened this issue Apr 23, 2025 · 2 comments · Fixed by #19282
Closed

Unable to create a service from a template #19281

jeremystretch opened this issue Apr 23, 2025 · 2 comments · Fixed by #19282
Assignees
Labels
severity: medium Results in substantial degraded or broken functionality for specfic workflows status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Milestone

Comments

@jeremystretch
Copy link
Member

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.

@jeremystretch jeremystretch added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation severity: medium Results in substantial degraded or broken functionality for specfic workflows and removed status: needs triage This issue is awaiting triage by a maintainer labels Apr 23, 2025
@jeremystretch jeremystretch self-assigned this Apr 23, 2025
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Apr 23, 2025
@jeremystretch
Copy link
Member Author

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
Copy link
Member Author

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 up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity: medium Results in substantial degraded or broken functionality for specfic workflows status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant