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

Fix infiniband misspelling #3556

New Issue
Closed
opened 2025-12-29 18:29:52 +01:00 by adam · 5 comments
adam commented 2025-12-29 18:29:52 +01:00
Owner
Copy Link

Originally created by @solj on GitHub (Apr 10, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 3.6.8
  • NetBox version: 2.7.10

Steps to Reproduce

  1. Try to add an infiniband interface via the API using the correct spelling.

Expected Behavior

The interface should be added.

Observed Behavior

The request failed with code 400 Bad Request: {'type': ['infiniband-hdr is not a valid choice.']}

Originally created by @solj on GitHub (Apr 10, 2020). Originally assigned to: @jeremystretch on GitHub. <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.6.8 * NetBox version: 2.7.10 <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox (or the current beta release where applicable). Begin with the creation of any necessary database objects and call out every operation being performed explicitly. If reporting a bug in the REST API, be sure to reconstruct the raw HTTP request(s) being made: Don't rely on a wrapper like pynetbox. --> ### Steps to Reproduce 1. Try to add an infiniband interface via the API using the correct spelling. <!-- What did you expect to happen? --> ### Expected Behavior The interface should be added. <!-- What happened instead? --> ### Observed Behavior The request failed with code 400 Bad Request: {'type': ['infiniband-hdr is not a valid choice.']}
adam added the type: bugstatus: accepted labels 2025-12-29 18:29:52 +01:00
adam closed this issue 2025-12-29 18:29:52 +01:00
adam commented 2025-12-29 18:29:52 +01:00
Author
Owner
Copy Link

@sdktr commented on GitHub (Apr 12, 2020):

What’s your exact API request that failes? From the current info it’s not deducible what your definition or ‘correct spelling’ entails? Merci!

@sdktr commented on GitHub (Apr 12, 2020): What’s your exact API request that failes? From the current info it’s not deducible what your definition or ‘correct spelling’ entails? Merci!
adam commented 2025-12-29 18:29:52 +01:00
Author
Owner
Copy Link

@solj commented on GitHub (Apr 12, 2020):

The problem is detailed in #4475. Basically, the current choices are spelled inifiband instead of infiniband.

@solj commented on GitHub (Apr 12, 2020): The problem is detailed in #4475. Basically, the current choices are spelled inifiband instead of infiniband.
adam commented 2025-12-29 18:29:52 +01:00
Author
Owner
Copy Link

@sdktr commented on GitHub (Apr 12, 2020):

Ah, missed that PR. Good ol’ inifiband, never made it to mainstream usage🤐

@sdktr commented on GitHub (Apr 12, 2020): Ah, missed that PR. Good ol’ inifiband, never made it to mainstream usage🤐
adam commented 2025-12-29 18:29:52 +01:00
Author
Owner
Copy Link

@kobayashi commented on GitHub (Apr 13, 2020):

Thanks to follow the template. I am accepting this for fixing the spell. Another maintainers will accept to go further.

@kobayashi commented on GitHub (Apr 13, 2020): Thanks to follow the template. I am accepting this for fixing the spell. Another maintainers will accept to go further.
adam commented 2025-12-29 18:29:52 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 13, 2020):

@kobayashi Just to clarify, the two-maintainer requirement is only for FRs. Only one approval is needed for confirmed bugs.

@jeremystretch commented on GitHub (Apr 13, 2020): @kobayashi Just to clarify, the two-maintainer requirement is only for FRs. Only one approval is needed for confirmed bugs.
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: 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#3556
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?