Fix incorrect tenancy display in related prefixes table #806
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #779
#779 describes a bug that we inadvertently introduced in #696 by cherry-picking several fixes from NetBox. In NetBox, the introduced bug (netbox-community/netbox#6108) was initially fixed in version 2.10.9 by removing the introduced incorrect logic (netbox-community/netbox@03b3f59), but a more complete fix was introduced by refactoring in version 2.11.x to provide a more general pattern for tenant reference columns (netbox-community/netbox@20a85c1), which was then slightly refined in netbox-community/netbox@0a1531c.
This PR therefore includes Nautobot-adapted versions of netbox-community/netbox@20a85c1 and netbox-community/netbox@0a1531c, both originally authored by @jeremystretch.
Before the fix - note that the "No Tenant" prefix in the right table incorrectly shows itself as belonging to the same tenant as the selected tenant:
After the fix - related prefix in the right table is correctly shown as having no tenant: