bug(DIRE): duplicate device showing up in inventory #781
Labels
No labels
1week
2weeks
Failed compliance check
IP cameras
NATS
Possible security concern
Review effort 1/5
Review effort 2/5
Review effort 3/5
Review effort 4/5
Review effort 5/5
UI
aardvark
accessibility
amd64
api
arm64
auth
back-end
bgp
blog
bug
build
checkers
ci-cd
cleanup
cnpg
codex
core
dependencies
device-management
documentation
duplicate
dusk
ebpf
enhancement
eta 1d
eta 1hr
eta 3d
eta 3hr
feature
fieldsurvey
github_actions
go
good first issue
help wanted
invalid
javascript
k8s
log-collector
mapper
mtr
needs-triage
netflow
network-sweep
observability
oracle
otel
plug-in
proton
python
question
reddit
redhat
research
rperf
rperf-checker
rust
sdk
security
serviceradar-agent
serviceradar-agent-gateway
serviceradar-web
serviceradar-web-ng
siem
snmp
sysmon
topology
ubiquiti
wasm
wontfix
zen-engine
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
carverauto/serviceradar#781
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Imported from GitHub.
Original GitHub issue: #2377
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2377
Original created: 2026-01-19T20:48:45Z
Describe the bug
tonka01is showing up in the device inventory indemo-stagingnamespace twice, has two different IP addresses.Presumably good
tonka01:https://staging.serviceradar.cloud/devices/sr%3A7588d12c-e8da-4b9e-a21d-8cc5c7faef38
Duplicate
tonka0:https://staging.serviceradar.cloud/devices/sr%3A1bb1b077-df44-4ef9-b4ab-127eed6af3bf
Both IP addresses are actual interfaces on the device (router), the DIRE (device identity and reconciliation engine) should have de-duplicated them into one device.
It is actually flipping IP addresses, when I originally saw it, it showed up with the same IP address for both devices, then a few minutes later they got two different IP addresses, now both tonka01's have converged around
216.17.46.98.Also the network sweep status that appeared when tonka01 showed up under
192.168.10.1is gone when both devices have their primary IP address set to216.17.46.98.We're also not showing any of the interfaces that we used to see under the interfaces tab that has now been moved underneath the device details screen, the interfaces tab isn't showing up for either of the tonka01 devices, presumably those interfaces were associated with tonka01 when it was known as
192.168.10.1, maybe after the next discovery/mapper job run they'll appear but it seems like that would be also keeping a double set of these interfaces in the database somewhere, also bad.To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.