[RFE] Detailed error responses for failed VPN connections

Bug #1692126 reported by Kevin Benton on 2017-05-19
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Wishlist
Unassigned

Bug Description

From https://etherpad.openstack.org/p/boston-vpnaas .

We need a way to report more details from a connection failure back to the user so they can get a hint on why a VPN connection failed.

tags: added: vpnaas
Changed in neutron:
status: New → Confirmed
tags: added: rfe
summary: - Detailed error responses for failed VPN connections
+ [RFE] Detailed error responses for failed VPN connections
Changed in neutron:
status: Confirmed → New

This makes sense across all neutron resources.

Changed in neutron:
status: New → Confirmed
importance: Undecided → Wishlist

Let's see if Kevin wants to expand the use case and have this be addressed as a "standard attribute".

Changed in neutron:
status: Confirmed → Triaged

Also a potential starter RFE

YAMAMOTO Takashi (yamamoto) wrote :

i agree it makes sense to add the "reason of status" field to any resouces with "status".
otoh, i'm not sure if it belongs to standard attributes. after all, not all resources have "status".

Miguel Lavalle (minsel) wrote :

Update after meeting on 10/12/2017. The consensus of the drivers team is that this is a reasonable addition to VPN. We will let the VPN team whether they want to continue with this

tags: added: rfe-approved
removed: rfe
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers