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

Device Type allows device bays without being set to parent #4432

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

Originally created by @n4zmz on GitHub (Jan 4, 2021).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 3.8.5
  • NetBox version: 2.10.2

Steps to Reproduce

  1. Device type add
    Manufacturer: IBM
    Model: store2
    Rest left at default (parent/child is ---------)
  2. click create
  3. click add components and select device bays
    Name: da[0-11]
  4. click create

Expected Behavior

Adding device bays should fail until device type is set to parent

Observed Behavior

Device bays are added, but can not be edited until parent is set.

Originally created by @n4zmz on GitHub (Jan 4, 2021). Originally assigned to: @jeremystretch on GitHub. <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for reporting reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, please start a discussion instead: https://github.com/netbox-community/netbox/discussions 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, and that any plugins have been disabled. --> ### Environment * Python version: 3.8.5 * NetBox version: 2.10.2 <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox. 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 client library such as pynetbox. --> ### Steps to Reproduce 1. Device type add Manufacturer: IBM Model: store2 Rest left at default (parent/child is ---------) 2. click create 3. click add components and select device bays Name: da[0-11] 4. click create <!-- What did you expect to happen? --> ### Expected Behavior Adding device bays should fail until device type is set to parent <!-- What happened instead? --> ### Observed Behavior Device bays are added, but can not be edited until parent is set.
adam added the type: bugstatus: accepted labels 2025-12-29 18:35:56 +01:00
adam closed this issue 2025-12-29 18:35:56 +01:00
adam commented 2025-12-29 18:35:57 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 5, 2021):

Would there be a significant impact from simply removing the parent role designation from DeviceType entirely? IIRC we used to have similar controls for the assignment of other components but ditched them a long time ago. It doesn't seem necessary.

@jeremystretch commented on GitHub (Jan 5, 2021): Would there be a significant impact from simply removing the parent role designation from DeviceType entirely? IIRC we used to have similar controls for the assignment of other components but ditched them a long time ago. It doesn't seem necessary.
adam commented 2025-12-29 18:35:57 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jan 6, 2021):

I don't see any potential impact. It would just make it so every parent could be a child.

I think there was 1 stipulation where a child couldn't be racked or something (would have to look at the errors generated) but I don't think it is a needed restriction.

@DanSheps commented on GitHub (Jan 6, 2021): I don't see any potential impact. It would just make it so every parent could be a child. I think there was 1 stipulation where a child couldn't be racked or something (would have to look at the errors generated) but I don't think it is a needed restriction.
adam commented 2025-12-29 18:35:57 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 6, 2021):

Ah, that's true, we do use it to restrict rackability.

@jeremystretch commented on GitHub (Jan 6, 2021): Ah, that's true, we do use it to restrict rackability.
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#4432
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?