neutron

[RFE] Detailed error responses for failed VPN connections

Bug #1692126 reported by Kevin Benton
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Triaged
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.

YAMAMOTO Takashi (yamamoto)
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
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

This makes sense across all neutron resources.

Changed in neutron:
status: New → Confirmed
importance: Undecided → Wishlist
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

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
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

Also a potential starter RFE

Revision history for this message
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".

Revision history for this message
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  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.