Replies: 2 comments 2 replies
-
This is weird. It works fine for me on a system migrated from 2.11.12 to 3.0.1:
A number of small bugs were fixed in 3.0.1, although I don't see this referred to in the release notes it might be worth upgrading before continuing. I cannot see why deleting and recreating the device identically would make a difference. Did you trim your API results? I see much more (e.g. interface types). Is it possible there was a cable between the devices, and it's showing interfaces where the other end is the same device_id? (I'm just clutching at straws here) And are you 100% sure you didn't have a URL typo like |
Beta Was this translation helpful? Give feedback.
-
Were these devices part of a virtual chassis by chance? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Problem
Hello,
i've just migrated from
Netbox v2.11.12
toNetbox 3.0
and frompostgres 12
topostgres 13
.After the migration the API call
api/dcim/interfaces/?device_id=364&name=Ethernet1%2F1
returns multiple results (multiple devices) even if thedevice_id
andinterface name
is specified.The result of API call:
As can be seen, the interface name matches, but the device_id is returned for devices 364 (nexus1) and 365 (nexus2) even if the
device_id = 365
is in the call.Quick fix
I've removed both devices (nexus1 and nexus2) and then I create them again in the Netbox. After the "re-creation" it works fine. But I don't want to recreate all devices, because I don't know where the problem could appear again. Also a lot of changelogs is generated when recreating devices.
My Postgres migration process
Netbox v2.11.12 + Postgre 12
- database backup (SQL)Netbox v.3.0 + Postgre 13
- clean database createdNetbox v3.0
migrationsQuestion
What could cause the problem with the API call?
Beta Was this translation helpful? Give feedback.
All reactions