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 reservations must be deleted before deleting a user #1364

New Issue
Closed
opened 2025-12-29 16:31:47 +01:00 by adam · 1 comment
adam commented 2025-12-29 16:31:47 +01:00
Owner
Copy Link

Originally created by @gmazoyer on GitHub (Oct 31, 2017).

Issue type

[ ] Feature request
[X] Bug report
[ ] Documentation

Environment

  • Python version: 2.7.12
  • NetBox version: 2.2.2

Description

When trying to delete a user that has made some rack reservations, Netbox expects these reservations to be deleted before deleting the user.

Steps to reproduce

  1. Create a user
  2. Login as the created user
  3. Create rack reservations inside a rack
  4. Login as administrator
  5. Delete the previously created user

Expected behavior

I'd expect the user to be deleted without needing to delete the rack reservations. For example, one of my colleague can do the some rack reservations but when he will leave the company (and remove his user account) reservations will most likely still be valid.

Screenshot

rack_reservations

Originally created by @gmazoyer on GitHub (Oct 31, 2017). ### Issue type [ ] Feature request [X] Bug report [ ] Documentation ### Environment * Python version: 2.7.12 * NetBox version: 2.2.2 ### Description When trying to delete a user that has made some rack reservations, Netbox expects these reservations to be deleted before deleting the user. #### Steps to reproduce 1) Create a user 2) Login as the created user 3) Create rack reservations inside a rack 4) Login as administrator 5) Delete the previously created user #### Expected behavior I'd expect the user to be deleted without needing to delete the rack reservations. For example, one of my colleague can do the some rack reservations but when he will leave the company (and remove his user account) reservations will most likely still be valid. #### Screenshot ![rack_reservations](https://user-images.githubusercontent.com/736209/32235634-53bf2826-be60-11e7-8c2b-8f1f04670fd0.png)
adam added the type: feature label 2025-12-29 16:31:47 +01:00
adam closed this issue 2025-12-29 16:31:47 +01:00
adam commented 2025-12-29 16:31:48 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 31, 2017):

Rack reservations are intentionally tied to a specific user. This is to prevent reservations from becoming disassociated with an owner and stagnating. However, you raise a good point in that the UI should provide a mechanism for easily reassigning a reservation's owner.

@jeremystretch commented on GitHub (Oct 31, 2017): Rack reservations are intentionally tied to a specific user. This is to prevent reservations from becoming disassociated with an owner and stagnating. However, you raise a good point in that the UI should provide a mechanism for easily reassigning a reservation's owner.
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 type: feature
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#1364
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?