Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to re-name Racks #4149

Closed
tanleach opened this issue Jul 21, 2023 · 2 comments · Fixed by #4232
Closed

Unable to re-name Racks #4149

tanleach opened this issue Jul 21, 2023 · 2 comments · Fixed by #4232
Assignees
Labels
emergent Unplanned work that is brought into a sprint after it's started. question Further information is requested type: bug Something isn't working as expected

Comments

@tanleach
Copy link

Environment

  • Nautobot version (Docker tag too if applicable): v1.5.23
  • Python version: 3.10
  • Database platform, version: Postgres
  • Middleware(s):

Steps to Reproduce

  1. Go to dcim/racks/
  2. select any rack to edit
  3. 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.

From Slack Conversation with Glenn M. it is suspected that #4025 may have introduced this.

@glennmatthews glennmatthews added the type: bug Something isn't working as expected label Jul 21, 2023
@glennmatthews glennmatthews self-assigned this Aug 9, 2023
@glennmatthews
Copy link
Contributor

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?

@glennmatthews glennmatthews added the question Further information is requested label Aug 9, 2023
@glennmatthews
Copy link
Contributor

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.

glennmatthews added a commit that referenced this issue Aug 9, 2023
@bryanculver bryanculver added the emergent Unplanned work that is brought into a sprint after it's started. label Aug 9, 2023
glennmatthews added a commit that referenced this issue Aug 9, 2023
* Fix #4149 - correct logic in RackForm

* Flake8

* Fix test
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 8, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
emergent Unplanned work that is brought into a sprint after it's started. question Further information is requested type: bug Something isn't working as expected
Projects
No open projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants