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

Error message logged on encountering NAPALM permissions #36

Open
glennmatthews opened this issue Apr 15, 2021 · 3 comments
Open

Error message logged on encountering NAPALM permissions #36

glennmatthews opened this issue Apr 15, 2021 · 3 comments
Labels
bug Something isn't working

Comments

@glennmatthews
Copy link
Contributor

glennmatthews commented Apr 15, 2021

Environment

  • Python version:
  • Nautobot version: 1.0.0b3
  • nautobot-netbox-importer version: 1.2.0

Expected Behavior

Successful import without error messages

Observed Behavior

15:00:22 error    Expected but did not find an existing Nautobot record
  source: user
  target: permission
  unique_id:
    {'codename': 'napalm_read', 'content_type': <ContentType: dcim | device>}
15:00:22 error    Expected but did not find an existing Nautobot record
  source: user
  target: permission
  unique_id:
    {'codename': 'napalm_write', 'content_type': <ContentType: dcim | device>}

(may be repeated multiple times)

Steps to Reproduce

  1. Import a dump from NetBox that has these permission records defined.
@glennmatthews glennmatthews added the bug Something isn't working label Apr 15, 2021
@glennmatthews
Copy link
Contributor Author

Nautobot doesn't actually use user.permission objects (it, like current versions of NetBox, uses a custom objectpermission model instead), so an appropriate fix here would likely be to ignore user.permission from the import altogether.

@hagaram
Copy link

hagaram commented Feb 10, 2022

Hello @glennmatthews,

is there a way how to import this kind of dump at the moment as I've encountered exactly the same issue?

I've naively tried to use --exclude auth.permission when exporting data from netbox, but of course it "exploded" when importing the data to nautobot.

Best regards,
Michal

@glennmatthews
Copy link
Contributor Author

This issue should be cosmetic only - it shouldn't cause the import as a whole to fail. If your import is failing likely something else is going wrong... can you perhaps open a new issue with the complete (or minimally redacted) logs from your failed import?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants