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

'str' object has no attribute 'is_cloneable' on Device "Create and Add Another" #7983

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

Originally created by @FenixVale on GitHub (May 2, 2023).

NetBox version

v3.5.0

Python version

3.10

Steps to Reproduce

  1. Click create a device
  2. Populate the information for the device
  3. Click "Create & Add Another"

Expected Behavior

A new page should load with much of the information pre-populated to continue created new devices

Observed Behavior

The error would appear instead.

<class 'AttributeError'>

'str' object has no attribute 'is_cloneable'

%Versions
Screenshot 2023-05-02 144948

Originally created by @FenixVale on GitHub (May 2, 2023). ### NetBox version v3.5.0 ### Python version 3.10 ### Steps to Reproduce 1. Click create a device 2. Populate the information for the device 3. Click "Create & Add Another" ### Expected Behavior A new page should load with much of the information pre-populated to continue created new devices ### Observed Behavior The error would appear instead. <class 'AttributeError'> 'str' object has no attribute 'is_cloneable' %Versions ![Screenshot 2023-05-02 144948](https://user-images.githubusercontent.com/33432475/235760460-e64dd133-0391-4316-856d-cf8972d72f86.png)
adam added the type: bug label 2025-12-29 20:30:50 +01:00
adam closed this issue 2025-12-29 20:30:50 +01:00
adam commented 2025-12-29 20:30:50 +01:00
Author
Owner
Copy Link

@FenixVale commented on GitHub (May 2, 2023):

Additional note, the issue appears to be very similar to Issue 12395, however I do not have any custom fields.

@FenixVale commented on GitHub (May 2, 2023): Additional note, the issue appears to be very similar to [Issue 12395](https://github.com/netbox-community/netbox/issues/12395), however I do not have any custom fields.
adam commented 2025-12-29 20:30:50 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 2, 2023):

I'm afraid the reproduction steps you've provided aren't sufficient to reproduce the issue. I'd be very surprised if it's not resolved by the fix for #12395 however.

@jeremystretch commented on GitHub (May 2, 2023): I'm afraid the reproduction steps you've provided aren't sufficient to reproduce the issue. I'd be very surprised if it's not resolved by the fix for #12395 however.
adam commented 2025-12-29 20:30:50 +01:00
Author
Owner
Copy Link

@FenixVale commented on GitHub (May 3, 2023):

I'm afraid the reproduction steps you've provided aren't sufficient to reproduce the issue. I'd be very surprised if it's not resolved by the fix for #12395 however.

Would this fix already have been implemented in the latest release, or will I have to do so manually / wait until next release? I executed my update this morning which was when the bug arose

@FenixVale commented on GitHub (May 3, 2023): > I'm afraid the reproduction steps you've provided aren't sufficient to reproduce the issue. I'd be very surprised if it's not resolved by the fix for #12395 however. Would this fix already have been implemented in the latest release, or will I have to do so manually / wait until next release? I executed my update this morning which was when the bug arose
adam commented 2025-12-29 20:30:51 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 3, 2023):

The fix has been merged into the develop branch and will ship with the upcoming v3.5.1 release, expected in the next day or two.

@jeremystretch commented on GitHub (May 3, 2023): The fix has been merged into the `develop` branch and will ship with the upcoming v3.5.1 release, expected in the next day or two.
adam commented 2025-12-29 20:30:51 +01:00
Author
Owner
Copy Link

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

Closing this out as it does not appear reproducible on the current stable release, and v3.5.1 has been released. Happy to re-open if suitable reproduction steps can be identified.

@jeremystretch commented on GitHub (May 5, 2023): Closing this out as it does not appear reproducible on the current stable release, and v3.5.1 has been released. Happy to re-open if suitable reproduction steps can be identified.
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 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#7983
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?