-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Closed
Labels
severity: mediumResults in substantial degraded or broken functionality for specfic workflowsResults in substantial degraded or broken functionality for specfic workflowsstatus: acceptedThis issue has been accepted for implementationThis issue has been accepted for implementationtype: bugA confirmed report of unexpected behavior in the applicationA confirmed report of unexpected behavior in the application
Description
Deployment Type
Self-hosted
NetBox Version
v3.7.0
Python Version
3.9
Steps to Reproduce
Setup for test device:
- Create site MySite
- Create manufacturer Test
- Create device type TestModel
- Create device role VPN
- Create device TestDevice (using the attribute values above)
- For the device, create interfaces tunnel.[1-2] (type = virtual)
- For the device, create interface Internet (type = f.ex. 1000base-T)
- For the Internet interface, add IP address 123.123.123.123/32
Now the actual VPN tunnels:
- Create VPN tunnel Tunnel1:
- encap = IPsec - Tunnel
- first termination:
- Role = Hub
- Type = Device
- Device = TestDevice
- Interface = tunnel.1
- Outside IP = 123.123.123.123/32
- Create another VPN tunnel Tunnel2:
- encap = IPsec - Tunnel
- first termination:
- Role = Hub
- Type = Device
- Device = TestDevice
- Interface = tunnel.2
- Outside IP = 123.123.123.123/32
Expected Behavior
Both tunnels and terminations are created successfully, as they will both terminate on the same Outside IP. That is the usual way of using several tunnels on the same device.
Observed Behavior
When pressing the Create button for the second tunnel:
"
Server Error
There was a problem with your request. Please contact an administrator.
The complete exception is provided below:
<class 'django.db.utils.IntegrityError'>
duplicate key value violates unique constraint "vpn_tunneltermination_outside_ip_id_key"
DETAIL: Key (outside_ip_id)=(14) already exists.
Python version: 3.9.2
NetBox version: 3.7.0
Plugins: None installed
"
Metadata
Metadata
Assignees
Labels
severity: mediumResults in substantial degraded or broken functionality for specfic workflowsResults in substantial degraded or broken functionality for specfic workflowsstatus: acceptedThis issue has been accepted for implementationThis issue has been accepted for implementationtype: bugA confirmed report of unexpected behavior in the applicationA confirmed report of unexpected behavior in the application