Skip to content
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

API call to add VPN tunnel fails: group field is required #15126

Closed
markkuleinio opened this issue Feb 13, 2024 · 0 comments · Fixed by #15136
Closed

API call to add VPN tunnel fails: group field is required #15126

markkuleinio opened this issue Feb 13, 2024 · 0 comments · Fixed by #15136
Assignees
Labels
severity: medium Results in substantial degraded or broken functionality for specfic workflows status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@markkuleinio
Copy link
Contributor

markkuleinio commented Feb 13, 2024

Deployment Type

Self-hosted

NetBox Version

v3.7.2

Python Version

3.11

Steps to Reproduce

$ curl -s -i http://netbox-test.lein.io/api/vpn/tunnels/ \
-H "Authorization: Token 176d4c04ccc8f2a549ea6fd393567d9da5a796ff" \
-H "Content-type: application/json" \
-H "Accept: application/json; indent=4" \
-d '{"name":"TestTunnel", "encapsulation":"ipsec-tunnel", "status":"active"}'

Expected Behavior

Tunnel "TestTunnel" is added successfully.

Observed Behavior

HTTP/1.1 400 Bad Request
API-Version: 3.7
...
{
    "group": [
        "This field is required."
    ]
}

Adding the same tunnel in GUI is successful (using only those three mandatory fields).

Workaround

Create a tunnel group like "TEMP", then add "group":1 (where 1 is the group ID) in the create call, and finally edit the resulted tunnel to remove the TEMP group.

@markkuleinio markkuleinio added the type: bug A confirmed report of unexpected behavior in the application label Feb 13, 2024
@jeremystretch jeremystretch self-assigned this Feb 13, 2024
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation severity: medium Results in substantial degraded or broken functionality for specfic workflows labels Feb 13, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
severity: medium Results in substantial degraded or broken functionality for specfic workflows status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
2 participants