Cloning a device type does not clone any interface or component #7865

Closed
opened 2025-12-29 20:29:10 +01:00 by adam · 2 comments
Owner

Originally created by @TnTBass on GitHub (Apr 5, 2023).

NetBox version

v3.4.7

Python version

3.10

Steps to Reproduce

  1. Select an existing device type with interfaces, console ports and power ports
  2. Select "Clone"
  3. Name your new device type

Expected Behavior

I would expect a clone of the device type to come with all interfaces/ports/etc for easier editing. There is no benefit to cloning a template over creating a brand new one.

Observed Behavior

Discover no interfaces, console ports or power ports come pre-populated

Originally created by @TnTBass on GitHub (Apr 5, 2023). ### NetBox version v3.4.7 ### Python version 3.10 ### Steps to Reproduce 1. Select an existing device type with interfaces, console ports and power ports 2. Select "Clone" 3. Name your new device type ### Expected Behavior I would expect a clone of the device type to come with all interfaces/ports/etc for easier editing. There is no benefit to cloning a template over creating a brand new one. ### Observed Behavior Discover no interfaces, console ports or power ports come pre-populated
adam closed this issue 2025-12-29 20:29:10 +01:00
Author
Owner

@jeremystretch commented on GitHub (Apr 5, 2023):

This is expected behavior, and consistent with the cloning of every other object type in NetBox. Replicating every related component has been proposed (see #5536) but no one has ever volunteered to own its implementation. You're welcome to open a new FR for it if you'd like to volunteer.

@jeremystretch commented on GitHub (Apr 5, 2023): This is expected behavior, and consistent with the cloning of every other object type in NetBox. Replicating every related component has been proposed (see #5536) but no one has ever volunteered to own its implementation. You're welcome to open a new FR for it if you'd like to volunteer.
Author
Owner

@jsenecal commented on GitHub (Apr 5, 2023):

This was proposed in https://github.com/netbox-community/netbox/issues/4065 and again in https://github.com/netbox-community/netbox/issues/5536 and https://github.com/netbox-community/netbox/issues/8840, but no one was interested in owning the implementation.

Edit: @jeremystretch beat me to it :D

@jsenecal commented on GitHub (Apr 5, 2023): This was proposed in https://github.com/netbox-community/netbox/issues/4065 and again in https://github.com/netbox-community/netbox/issues/5536 and https://github.com/netbox-community/netbox/issues/8840, but no one was interested in owning the implementation. Edit: @jeremystretch beat me to it :D
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7865