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 edit seems to be affect Device itself #1958

New Issue
Closed
opened 2025-12-29 17:20:56 +01:00 by adam · 1 comment
adam commented 2025-12-29 17:20:56 +01:00
Owner
Copy Link

Originally created by @a31amit on GitHub (Aug 20, 2018).

Environment

  • Python version: 3.4
  • NetBox version: 2.4.3

Changing Device Type Templates also have the effect on Device itself. As per understanding from net box documentation that device types are being used when someone creates the device and changing device type doesn't have the effect on the device itself. However in this case device type seems to have some effect on the device.

Split from - https://github.com/digitalocean/netbox/issues/2370

Steps to Reproduce

Create a Parent Chassis Device Type
Create a Device Based with same Device Type Model
Delete Bay in Device Type and Edit Device type from Parent to None
Open Device created with the same template and Select All Bay and Delete

Expected Behavior

it should redirect to Device page itself and also it should give the option to create/add device bay as well.
As per understanding from net box documentation that device types are being used when someone creates the device and changing device type doesn't have the effect on the device itself.

Observed Behavior

Taking back to home and when you open the device page for the same device, device bay area is missing from that device.

Originally created by @a31amit on GitHub (Aug 20, 2018). <!-- NOTE: 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.4 * NetBox version: 2.4.3 Changing Device Type Templates also have the effect on Device itself. As per understanding from net box documentation that device types are being used when someone creates the device and changing device type doesn't have the effect on the device itself. However in this case device type seems to have some effect on the device. Split from - https://github.com/digitalocean/netbox/issues/2370 ### Steps to Reproduce Create a Parent Chassis Device Type Create a Device Based with same Device Type Model Delete Bay in Device Type and Edit Device type from Parent to None Open Device created with the same template and Select All Bay and Delete <!-- What did you expect to happen? --> ### Expected Behavior it should redirect to Device page itself and also it should give the option to create/add device bay as well. As per understanding from net box documentation that device types are being used when someone creates the device and changing device type doesn't have the effect on the device itself. <!-- What happened instead? --> ### Observed Behavior Taking back to home and when you open the device page for the same device, device bay area is missing from that device.
adam closed this issue 2025-12-29 17:20:56 +01:00
adam commented 2025-12-29 17:20:56 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 20, 2018):

This is expected behavior. The device type is no longer designated as a parent device, so NetBox doesn't give you the option to add device bays. (Device bays are displayed if they've already been created, though.)

@jeremystretch commented on GitHub (Aug 20, 2018): This is expected behavior. The device type is no longer designated as a parent device, so NetBox doesn't give you the option to add device bays. (Device bays are displayed if they've already been created, though.)
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
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#1958
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?