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

"Create and add another" - Rack Position not accepted #4378

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

Originally created by @joni1993 on GitHub (Dec 18, 2020).

Environment

  • Python version: 3.6.9
  • NetBox version: v2.10.1

Steps to Reproduce

  1. Add Device to Rack Position
  2. Fill out as needed
  3. Select Rack Position
  4. Add Device via "Create and Add another" button
  5. Object ist created, form open again
  6. Select available rack position
  7. Try to create Object (either "Create" or "Create and Add Another"
  8. Form complains on Rack position "Select a valid choice. XX is not one of the available choices." (Where XX is chosen position number)

Expected Behavior

Observed Behavior

"Create and Add Another" Button should not

Workaround

Don't use the "Create and Add Another" button - Instead use Create, use the browser back button and submit the form again with updated position

Originally created by @joni1993 on GitHub (Dec 18, 2020). ### Environment * Python version: 3.6.9 * NetBox version: v2.10.1 ### Steps to Reproduce 1. Add Device to Rack Position 2. Fill out as needed 3. Select Rack Position 4. Add Device via "Create and Add another" button 5. Object ist created, form open again 6. Select available rack position 7. Try to create Object (either "Create" or "Create and Add Another" 8. Form complains on Rack position "Select a valid choice. XX is not one of the available choices." (Where XX is chosen position number) <!-- What did you expect to happen? --> ### Expected Behavior <!-- What happened instead? --> ### Observed Behavior "Create and Add Another" Button should not ### Workaround Don't use the "Create and Add Another" button - Instead use Create, use the browser back button and submit the form again with updated position
adam added the type: bugstatus: duplicate labels 2025-12-29 18:35:25 +01:00
adam closed this issue 2025-12-29 18:35:25 +01:00
adam commented 2025-12-29 18:35:26 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Dec 18, 2020):

Have you added the rack face? If you set a rack position you also need to set a rack face. If not, you get a less then helpful message relating to the position however it is the face that is the problem.

There is already a bug relating to this. Otherwise, I cannot recreate this on master.netbox.dev

@DanSheps commented on GitHub (Dec 18, 2020): Have you added the rack face? If you set a rack position you also need to set a rack face. If not, you get a less then helpful message relating to the position however it is the face that is the problem. There is already a bug relating to this. Otherwise, I cannot recreate this on master.netbox.dev
adam commented 2025-12-29 18:35:26 +01:00
Author
Owner
Copy Link

@joni1993 commented on GitHub (Dec 18, 2020):

Ok thats odd - i didn't noticed the rack face gets unset on "add another". Either the error message should be more clear or the face should not get reset.

@joni1993 commented on GitHub (Dec 18, 2020): Ok thats odd - i didn't noticed the rack face gets unset on "add another". Either the error message should be more clear or the face should not get reset.
adam commented 2025-12-29 18:35:26 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 18, 2020):

Either the error message should be more clear or the face should not get reset.

I haven't checked the behavior myself, but it sounds like a bug. Let's keep this issue open.

@jeremystretch commented on GitHub (Dec 18, 2020): > Either the error message should be more clear or the face should not get reset. I haven't checked the behavior myself, but it sounds like a bug. Let's keep this issue open.
adam commented 2025-12-29 18:35:27 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Dec 18, 2020):

Duplicate of #5301

@DanSheps commented on GitHub (Dec 18, 2020): Duplicate of #5301
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: duplicate 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#4378
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?