Replies: 2 comments 3 replies
-
I can't speak for the authors, but I would guess because it was an oversight to allow it in the first place: e.g. allowing a device called "foo" and another device called "Foo" in the same site for the same tenant, is confusing and error-prone. In that case, you might as well allow two devices called "foo".
You can use a SQL query to find them:
How to fix them depends on what your naming policy is. For example, given two devices called "UNDERL-0014" and "underl-0014" in the same site, what are your preferred new names? If you want to script the fixups, you should do it via nbshell, a custom script, or the REST API. Direct SQL updates to |
Beta Was this translation helpful? Give feedback.
-
Thank you very much ! I had just this one duplicate. After changing name, upgrade finished OK |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi
I am unable to upgrade netbox from 3.3.6 to latest ver. due to this braking changes in 3.4.0
...Device and virtual machine names are no longer case-sensitive. Attempting to create e.g. "device1" and "DEVICE1" within the same site will raise a validation error
Why this major change was implemented ?
I believe I am not only one who has problem with upgrade.
Any idea how to fix this effective way ?
When I remove/rename/fix one device and run upgrade, then another duplicate is found...there can be hundreds...:(
How can I make list of all "duplicates" from DB in once ?
How you fixed this ?
Beta Was this translation helpful? Give feedback.
All reactions