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

"Provider_account" field is required when bulk import circuits #8302

New Issue
Closed
opened 2025-12-29 20:35:07 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:35:07 +01:00
Owner
Copy Link

Originally created by @pharalambiev on GitHub (Jul 6, 2023).

NetBox version

3.5.0

Python version

3.9

Steps to Reproduce

When I try to bulk import circuits, attribute "Provider_account" is required.
As it is not mandatory when create circuits one by one, I was wondering if this is not some kind of bug or something.
More over, we are not using provider accounts at all.

Even though, I create a dummy provider account it must be attached to the provider itself.
Also, every provider name must be unique value, so I cannot create provider accounts with the same name (like Default) for each provider.
Having different account names for each provider is not working for me as I cannot easily match circuits with providers and their respective provider accounts. It would take me more time than to create circuits from scratch.

Expected Behavior

Expected behaviour for me would be provider accounts to be not required when bulk import circuits.

Observed Behavior

Provider account is required when bulk import circuits;
Provider account name must be unique when bulk import, even though I'm allowed to create/import multiple provider accounts with the same name.

Originally created by @pharalambiev on GitHub (Jul 6, 2023). ### NetBox version 3.5.0 ### Python version 3.9 ### Steps to Reproduce When I try to bulk import circuits, attribute "Provider_account" is required. As it is not mandatory when create circuits one by one, I was wondering if this is not some kind of bug or something. More over, we are not using provider accounts at all. Even though, I create a dummy provider account it must be attached to the provider itself. Also, every provider name must be unique value, so I cannot create provider accounts with the same name (like Default) for each provider. Having different account names for each provider is not working for me as I cannot easily match circuits with providers and their respective provider accounts. It would take me more time than to create circuits from scratch. ### Expected Behavior Expected behaviour for me would be provider accounts to be not required when bulk import circuits. ### Observed Behavior Provider account is required when bulk import circuits; Provider account name must be unique when bulk import, even though I'm allowed to create/import multiple provider accounts with the same name.
adam added the status: duplicate label 2025-12-29 20:35:07 +01:00
adam closed this issue 2025-12-29 20:35:07 +01:00
adam commented 2025-12-29 20:35:08 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (Jul 6, 2023):

Thank you for opening a bug report. I was unable to reproduce the reported behavior on NetBox v3.5.4. Please re-confirm the reported behavior on the current stable release and adjust your post above as necessary. Remember to provide detailed steps that someone else can follow using a clean installation of NetBox to reproduce the issue. Remember to include the steps taken to create any initial objects or other data.

@abhi1693 commented on GitHub (Jul 6, 2023): Thank you for opening a bug report. I was unable to reproduce the reported behavior on NetBox v3.5.4. Please re-confirm the reported behavior on the current stable release and adjust your post above as necessary. Remember to provide detailed steps that someone else can follow using a clean installation of NetBox to reproduce the issue. Remember to include the steps taken to create any initial objects or other data.
adam commented 2025-12-29 20:35:08 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Jul 6, 2023):

Duplicate of https://github.com/netbox-community/netbox/issues/12396

Fixed in https://github.com/netbox-community/netbox/pull/12407

@kkthxbye-code commented on GitHub (Jul 6, 2023): Duplicate of https://github.com/netbox-community/netbox/issues/12396 Fixed in https://github.com/netbox-community/netbox/pull/12407
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
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#8302
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?