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

Platform manufacturer filtering is inconsistent - allows selection after removal but not before #11874

New Issue
Open
opened 2025-12-29 21:51:04 +01:00 by adam · 4 comments
adam commented 2025-12-29 21:51:04 +01:00
Owner
Copy Link

Originally created by @cuorenero92 on GitHub (Nov 26, 2025).

NetBox Edition

NetBox Community

NetBox Version

v4.4.6

Python Version

3.12

Steps to Reproduce

NetBox version: v4.4.6
Python version: 3.13.5

Steps to Reproduce:

  1. Create a Platform with a specific Manufacturer (e.g., OPNsense with manufacturer "Deciso")
  2. Create a Device with a different Device Type manufacturer (e.g., Protectli)
  3. Try to assign the Platform to the Device via the Platform dropdown
  4. Expected: Platform should be available for selection (or not, consistently)
  5. Actual: Platform is NOT shown in dropdown. But if you remove the manufacturer from the Platform first, you can select it, then re-add the manufacturer afterward

Expected Behavior

Either the filter should prevent selection entirely, OR it should allow selection regardless of manufacturer mismatch.

Observed Behavior

The filter prevents selection during the form but allows the same "invalid" state after saving if you remove and re-add the manufacturer.

Originally created by @cuorenero92 on GitHub (Nov 26, 2025). ### NetBox Edition NetBox Community ### NetBox Version v4.4.6 ### Python Version 3.12 ### Steps to Reproduce NetBox version: v4.4.6 Python version: 3.13.5 Steps to Reproduce: 1. Create a Platform with a specific Manufacturer (e.g., OPNsense with manufacturer "Deciso") 2. Create a Device with a different Device Type manufacturer (e.g., Protectli) 3. Try to assign the Platform to the Device via the Platform dropdown 4. Expected: Platform should be available for selection (or not, consistently) 5. Actual: Platform is NOT shown in dropdown. But if you remove the manufacturer from the Platform first, you can select it, then re-add the manufacturer afterward ### Expected Behavior Either the filter should prevent selection entirely, OR it should allow selection regardless of manufacturer mismatch. ### Observed Behavior The filter prevents selection during the form but allows the same "invalid" state after saving if you remove and re-add the manufacturer.
adam added the type: bugstatus: needs ownernetboxseverity: low labels 2025-12-29 21:51:04 +01:00
adam commented 2025-12-29 21:51:05 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 26, 2025):

  1. Expected: Platform should be available for selection (or not, consistently)

The platform you created in step 1 is not an available option because it has been restricted to a different manufacturer. This is expected behavior.

But if you remove the manufacturer from the Platform first, you can select it, then re-add the manufacturer afterward

So the only inconsistency here is that a platform may have a manufacturer assigned despite itself being selected by one or more devices with a different manufacturer. I'm not sure it's worth the effort to enforce such a restriction, but I'll open this for volunteers.

@jeremystretch commented on GitHub (Nov 26, 2025): > 4. Expected: Platform should be available for selection (or not, consistently) The platform you created in step 1 is not an available option because it has been restricted to a different manufacturer. This is expected behavior. > But if you remove the manufacturer from the Platform first, you can select it, then re-add the manufacturer afterward So the only inconsistency here is that a platform may have a manufacturer assigned despite itself being selected by one or more devices with a different manufacturer. I'm not sure it's worth the effort to enforce such a restriction, but I'll open this for volunteers.
adam commented 2025-12-29 21:51:05 +01:00
Author
Owner
Copy Link

@cuorenero92 commented on GitHub (Nov 27, 2025):

I don't understand how to register my items correctly then.

A common example: an HP workstation running Microsoft Windows. The hardware manufacturer (HP) is completely unrelated to the OS manufacturer (Microsoft), yet NetBox would prevent assigning Windows as the platform because the manufacturers don't match.

In my case: a Protectli firewall running OPNsense - same issue. How should I handle this in NetBox?

@cuorenero92 commented on GitHub (Nov 27, 2025): I don't understand how to register my items correctly then. A common example: an HP workstation running Microsoft Windows. The hardware manufacturer (HP) is completely unrelated to the OS manufacturer (Microsoft), yet NetBox would prevent assigning Windows as the platform because the manufacturers don't match. In my case: a Protectli firewall running OPNsense - same issue. How should I handle this in NetBox?
adam commented 2025-12-29 21:51:05 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 27, 2025):

You would not assign a manufacturer to the Windows operating system, because it is not limited to deployment on a specific set of hardware. This unlike e.g. Cisco IOS, which can be deployed only on Cisco hardware.

@jeremystretch commented on GitHub (Nov 27, 2025): You would not assign a manufacturer to the Windows operating system, because it is not limited to deployment on a specific set of hardware. This unlike e.g. Cisco IOS, which can be deployed only on Cisco hardware.
adam commented 2025-12-29 21:51:06 +01:00
Author
Owner
Copy Link

@cuorenero92 commented on GitHub (Nov 27, 2025):

Thank you for the clarification! That makes sense now. I'll remove the manufacturer from the OPNsense platform since it's not hardware-specific, just like Windows.

I appreciate the explanation.

@cuorenero92 commented on GitHub (Nov 27, 2025): Thank you for the clarification! That makes sense now. I'll remove the manufacturer from the OPNsense platform since it's not hardware-specific, just like Windows. I appreciate the explanation.
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 netbox severity: low status: needs owner 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#11874
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?