-
Notifications
You must be signed in to change notification settings - Fork 51
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
Missing object imports in duplicate RPSL keys in the same source #560
Milestone
Comments
Your idea how to fix it makes sense to me |
mxsasha
added a commit
that referenced
this issue
Nov 30, 2021
2 tasks
mxsasha
added a commit
that referenced
this issue
Nov 30, 2021
mxsasha
added a commit
that referenced
this issue
Nov 30, 2021
mxsasha
added a commit
that referenced
this issue
Dec 1, 2021
mxsasha
added a commit
that referenced
this issue
Dec 1, 2021
There's probably still an issue with deletions: irrd/irrd/storage/database_handler.py Lines 381 to 382 in e8ecaa3
|
mxsasha
added a commit
that referenced
this issue
Jun 23, 2022
mxsasha
added a commit
that referenced
this issue
Jun 23, 2022
mxsasha
added a commit
that referenced
this issue
Jun 23, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
IRRDv4 is built on the assumption that the primary key is unique in each source. However, this is not true, and causes IRRD to miss objects.
The scale of this is unknown, but this has been the case since before 4.0.0, so likely not too widespread. It also has not come up in the many v3/v4 consistency checks.
One case is AS-DONNATRANS, which is both a mntner and as-set in RIPE. The import of one probably overwrites the other. Regardless of whether this is a good way to name objects, or should or should not be valid, it is a thing people do, so should be supported.
Probably the right fix is for IRRd to treat object class, RPSL pk, and source as unique together.
The text was updated successfully, but these errors were encountered: