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

Rack assigned to rack-group and site, which does not contain that rack-group #4483

New Issue
Closed
opened 2025-12-29 18:36:31 +01:00 by adam · 4 comments
adam commented 2025-12-29 18:36:31 +01:00
Owner
Copy Link

Originally created by @lucker7777 on GitHub (Jan 21, 2021).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: Python 3.9.1
  • NetBox version: 2.10.3

Steps to Reproduce

  1. Click on "Add" in Racks page
  2. In "Add a new rack" page, first choose "Group"
  3. Next, choose a "Site", but choose a site, which does not contain group from the previous step
  4. Add a rack name and click "Create"
  5. Now you have a rack located in a wrong site, which does not contain chosen RackGroup

Expected Behavior

I expect Netbox to not allow me to assign a rack to a wrong site.
For example, if you first choose "Site" in the "Add a new rack" page, then Netbox will filter other "Group" options.

Observed Behavior

Netbox will create the rack with wrong site

image
image

Originally created by @lucker7777 on GitHub (Jan 21, 2021). Originally assigned to: @jeremystretch on GitHub. ### Environment * Python version: Python 3.9.1 * NetBox version: 2.10.3 ### Steps to Reproduce 1. Click on "Add" in Racks page 2. In "Add a new rack" page, **first** choose "Group" 3. Next, choose a "Site", but choose a site, which does not contain group from the previous step 4. Add a rack name and click "Create" 5. Now you have a rack located in a wrong site, which does not contain chosen RackGroup ### Expected Behavior I expect Netbox to not allow me to assign a rack to a wrong site. For example, if you first choose "Site" in the "Add a new rack" page, then Netbox will filter other "Group" options. ### Observed Behavior Netbox will create the rack with wrong site ![image](https://user-images.githubusercontent.com/8921396/105372990-79ebfc80-5c06-11eb-8ae4-781d8441d86c.png) ![image](https://user-images.githubusercontent.com/8921396/105373079-9425da80-5c06-11eb-9684-7df79358eaa8.png)
adam added the type: bugstatus: accepted labels 2025-12-29 18:36:31 +01:00
adam closed this issue 2025-12-29 18:36:31 +01:00
adam commented 2025-12-29 18:36:32 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jan 21, 2021):

Related: #5311

@DanSheps commented on GitHub (Jan 21, 2021): Related: #5311
adam commented 2025-12-29 18:36:32 +01:00
Author
Owner
Copy Link

@lucker7777 commented on GitHub (Jan 21, 2021):

Hello,
can anybody estimate the complexity of the fix to this bug? Can this be fixed in a release or two?
I am a SW engineer at a university and we are currently trying to migrate the data from proprietary SW to Netbox and this bug can cause a lot of troubles as our staff is not accustomed to Netbox (or a similar SW), so they could produce a lot of inconsistencies between Sites and RackGroups.

Thanks.

@lucker7777 commented on GitHub (Jan 21, 2021): Hello, can anybody estimate the complexity of the fix to this bug? Can this be fixed in a release or two? I am a SW engineer at a university and we are currently trying to migrate the data from proprietary SW to Netbox and this bug can cause a lot of troubles as our staff is not accustomed to Netbox (or a similar SW), so they could produce a lot of inconsistencies between Sites and RackGroups. Thanks.
adam commented 2025-12-29 18:36:32 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jan 25, 2021):

There are a lot of issues with site/rack/device consistency as far as checking, however one way to handle this would be a custom script that will validate the status of the data in netbox to see if it is consistent or not.

@DanSheps commented on GitHub (Jan 25, 2021): There are a lot of issues with site/rack/device consistency as far as checking, however one way to handle this would be a custom script that will validate the status of the data in netbox to see if it is consistent or not.
adam commented 2025-12-29 18:36:32 +01:00
Author
Owner
Copy Link

@lucker7777 commented on GitHub (Jan 26, 2021):

Thank you all for a quick response and a quick fix :)

@lucker7777 commented on GitHub (Jan 26, 2021): Thank you all for a quick response and a quick fix :)
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 status: accepted 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#4483
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?