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

Rackgroup names should only be unique within a parent group #4195

New Issue
Closed
opened 2025-12-29 18:33:48 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:33:48 +01:00
Owner
Copy Link

Originally created by @martink2 on GitHub (Oct 17, 2020).

Environment

  • Python version: 3.6.9
  • NetBox version: 2.9.3

After the upgrade to 2.9 we are trying to use the
hierarchical rack groups to introduce a proper
representation of our DC environment like:

DC1
-Cage1
--Row1
---Rack1
-Cage2
--Row1
---Rack1
--Row2
---Rack1
---Rack2

Steps to Reproduce

  1. In site A create rack group Cage1
  2. In site A create rack group Cage2
  3. In site A create rack group Row1 with parent Cage1
  4. In site A create rack group Row1 with parent Cage2

Expected Behavior

We would expect that the name of a group must only be unique within its parent group
as is allowed with racks (two racks in the same site can have the same name in different groups).

Observed Behavior

Following error is given on creation of the second Row1:

Rack group with this Site and Name already exists.
Rack group with this Site and Slug already exists.
Originally created by @martink2 on GitHub (Oct 17, 2020). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/g/netbox-discuss Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report, and that any plugins have been disabled. --> ### Environment * Python version: 3.6.9 * NetBox version: 2.9.3 After the upgrade to 2.9 we are trying to use the hierarchical rack groups to introduce a proper representation of our DC environment like: DC1 -Cage1 --Row1 ---Rack1 -Cage2 --Row1 ---Rack1 --Row2 ---Rack1 ---Rack2 ### Steps to Reproduce 1. In site A create rack group Cage1 2. In site A create rack group Cage2 3. In site A create rack group Row1 with parent Cage1 4. In site A create rack group Row1 with parent Cage2 <!-- What did you expect to happen? --> ### Expected Behavior We would expect that the name of a group must only be unique within its parent group as is allowed with racks (two racks in the same site can have the same name in different groups). <!-- What happened instead? --> ### Observed Behavior Following error is given on creation of the second Row1: ``` Rack group with this Site and Name already exists. Rack group with this Site and Slug already exists. ```
adam added the status: revisions needed label 2025-12-29 18:33:48 +01:00
adam closed this issue 2025-12-29 18:33:48 +01:00
adam commented 2025-12-29 18:33:48 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 19, 2020):

Thank you for opening a bug report. It seems that the described functionality is intended behavior. If you meant to open a feature request instead, please close this issue and open a new one using the feature request template. Otherwise, please revise your post above to elaborate on why you believe the observed behavior is flawed.

@jeremystretch commented on GitHub (Oct 19, 2020): Thank you for opening a bug report. It seems that the described functionality is intended behavior. If you meant to open a feature request instead, please close this issue and open a new one using the [feature request template](https://github.com/netbox-community/netbox/issues/new?template=feature_request.md). Otherwise, please revise your post above to elaborate on why you believe the observed behavior is flawed.
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: revisions needed
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#4195
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?