Server Error when accessing VPN tunnels terminations tab

[mwitczak86]

Deployment Type

Self-hosted

NetBox Version

v4.1.4

Python Version

3.10

Steps to Reproduce

1. Create a VPN tunnel
2. Create a terminations on dcim.interface and virtualization.vminterface
3. Assign an outside IP for virtualization.vminterface
4. Click on VPN tunnel terminations tab

Expected Behavior

VPN tunnel terminations list is visible.

Observed Behavior

Server Error
There was a problem with your request. Please contact an administrator.

The complete exception is provided below:

<class 'django.core.exceptions.FieldError'>

Field 'termination' does not generate an automatic reverse relation and therefore cannot be used for reverse querying. If it is a GenericForeignKey, consider adding a GenericRelation.

Python version: 3.10.12
NetBox version: 4.1.4
Plugins:
django3_saml2_nbplugin: 2.0
netbox_documents: 0.7.0
netbox_inventory: 2.1.0
netbox_reorder_rack: 1.1.3
nextbox_ui_plugin: 1.0.7
If further assistance is required, please post to the NetBox discussion forum on GitHub.

[mwitczak86]

After deleting the newly created vpn entries, the problem persists. The vpn terminations are no longer visible within the tunnel object details. However, all database entries exists and are visible in the API queries. I am unable to restore NetBox to the state it was in before the issue occured. Thanks

[jnovinger]

@mwitczak86 , thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.

[github-actions]

This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.

[github-actions]

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

[jnovinger]

This appears to be the same issue as tracked down in #19487. We will include a fix there.