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

api devices export fails #7397

Closed
rfdrake opened this issue Sep 29, 2021 · 1 comment
Closed

api devices export fails #7397

rfdrake opened this issue Sep 29, 2021 · 1 comment
Assignees
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@rfdrake
Copy link
Contributor

rfdrake commented Sep 29, 2021

NetBox version

v3.0.4

Python version

3.9

Steps to Reproduce

  1. Create an export template. Name: g, Content Type: dcim | devices. Query: {{ queryset }}
  2. perform an api call to https://netbox/api/dcim/devices/?export=g
  3. error: 'NoneType' object has no attribute 'Meta'
  4. move the export template to dcim | sites
  5. rerun api call to https://netbox/api/dcim/sites/?export=g
  6. success

Expected Behavior

The export template should be run, the same way as if it is run in the netbox site UI.

Observed Behavior

<class 'AttributeError'>
'NoneType' object has no attribute 'Meta' Python version: 3.9.5 NetBox version: 3.0.4
@rfdrake rfdrake added the type: bug A confirmed report of unexpected behavior in the application label Sep 29, 2021
@rfdrake
Copy link
Contributor Author

rfdrake commented Sep 29, 2021

I tried this on v3.0.3 at first and had the same issue. I upgraded to 3.0.4 to see if it was fixed.

I also ran this against the public netbox demo because i wanted to make sure that my devices data wasn't somehow corrupted and causing the issue. I saw the same thing on that site, so I don't think it's my data. It may still be something I'm just doing wrong. This is the first time I've tried to use export templates via the API.

@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label Sep 30, 2021
@jeremystretch jeremystretch self-assigned this Sep 30, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 29, 2021
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