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

Power Feed export & import #2837

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

Originally created by @ryanmerolle on GitHub (Aug 28, 2019).

Environment

  • Python version: 3.6.8
  • NetBox version: 2.6.2

It seems the power feed data model or at least the export/import function is wrong.

Steps to Reproduce

  1. Export a group of Power feeds and review the export. You will find the following:
  • site column lists the panel_name
  • panel_name lists the rack_name
  • rack_group lists the nane
  • rack_name lists the status
  • name lists the type
  • status lists the supply
  • type lists the phase
  • supply lists the voltage
  • phase lists the amperage
  • voltage lists the max_utilization
  • amperage lists the comments
  • max_utilization - I am not sure what it lists as it is empty even though I filled out all fields
  • comments - I am not sure what it lists as it is empty even though I filled out all fields
  1. Imports seem to have a similar issues with mappings given the data model checks error out

Expected Behavior

I expected everything to map correctly on imports and exports. I am not sure if it is an issue that that specific function OR the data model.

Observed Behavior

See the mapping I mentioned in steps to reproduce. I can provide more detail if needed.

Originally created by @ryanmerolle on GitHub (Aug 28, 2019). ### Environment * Python version: 3.6.8 * NetBox version: 2.6.2 It seems the power feed data model or at least the export/import function is wrong. ### Steps to Reproduce 1. Export a group of Power feeds and review the export. You will find the following: * site column lists the panel_name * panel_name lists the rack_name * rack_group lists the nane * rack_name lists the status * name lists the type * status lists the supply * type lists the phase * supply lists the voltage * phase lists the amperage * voltage lists the max_utilization * amperage lists the comments * max_utilization - I am not sure what it lists as it is empty even though I filled out all fields * comments - I am not sure what it lists as it is empty even though I filled out all fields 2. Imports seem to have a similar issues with mappings given the data model checks error out <!-- What did you expect to happen? --> ### Expected Behavior I expected everything to map correctly on imports and exports. I am not sure if it is an issue that that specific function OR the data model. <!-- What happened instead? --> ### Observed Behavior See the mapping I mentioned in steps to reproduce. I can provide more detail if needed.
adam added the type: bugstatus: accepted labels 2025-12-29 18:22:41 +01:00
adam closed this issue 2025-12-29 18:22:41 +01:00
adam commented 2025-12-29 18:22:41 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Aug 29, 2019):

It looks like the table and associated data looks good in postgres. This just seems like a mapping issue in the export/import functions.

@ryanmerolle commented on GitHub (Aug 29, 2019): It looks like the table and associated data looks good in postgres. This just seems like a mapping issue in the export/import functions.
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#2837
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?