Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Power Feed export & import #3463

Closed
ryanmerolle opened this issue Aug 28, 2019 · 1 comment
Closed

Power Feed export & import #3463

ryanmerolle opened this issue Aug 28, 2019 · 1 comment
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@ryanmerolle
Copy link
Contributor

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.

@ryanmerolle ryanmerolle changed the title Power Feed export Power Feed export & import Aug 29, 2019
@ryanmerolle
Copy link
Contributor Author

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

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application labels Oct 9, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jan 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants