You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
tanleach opened this issue
Jul 21, 2023
· 2 comments
· Fixed by #4232
Assignees
Labels
emergentUnplanned work that is brought into a sprint after it's started.questionFurther information is requestedtype: bugSomething isn't working as expected
Nautobot version (Docker tag too if applicable): v1.5.23
Python version: 3.10
Database platform, version: Postgres
Middleware(s):
Steps to Reproduce
Go to dcim/racks/
select any rack to edit
change the name of the rack
Expected Behavior
Page would reload and name would be reflected.
Observed Behavior
When submitting an error shows up below the name field:
Device with `name` in ['2.5 960GB SSD (PCIE Gen3) Samsung', '40GBE Active Fiber Cable - Aqua - 03M', '40GBE Active Fiber Cable - Aqua - 05M', ... '2.5 960GB SSD Intel'] and site=A52Plus already exists.
I'm unable to reproduce this issue on demo.nautobot.com at present - I can successfully rename a Rack that contains Devices with no error. Can you provide more specific data that needs to be present to trigger the issue?
I think I've been able to reproduce this symptom by first cloning a device from the Rack in question into another Site (same device name, different site). Would still be good to confirm whether there are other scenarios that introduce this issue.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
emergentUnplanned work that is brought into a sprint after it's started.questionFurther information is requestedtype: bugSomething isn't working as expected
Environment
Steps to Reproduce
Expected Behavior
Page would reload and name would be reflected.
Observed Behavior
When submitting an error shows up below the
name
field:From Slack Conversation with Glenn M. it is suspected that #4025 may have introduced this.
The text was updated successfully, but these errors were encountered: