[VPNSERVICE-24] VPN interface operational not getting created Created: 21/Jan/16  Updated: 03/May/18  Resolved: 29/Jan/16

Status: Resolved
Project: vpnservice
Component/s: General
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: RajaRajan Manickam Assignee: RajaRajan Manickam
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Severity: critical
External issue ID: 5044

 Description   

VPN interface operational not getting created.But, config data store has all the required information.

Steps:

Create tunnel
create network
create subnet
create port
create l3vpn using cli.

Verify the following status:

IETF interface(config and operational)
IETF Interface state operational.
VPN instance config data store
VPN interface config data store.
VPN interface operational data store.

Result:
VPN operational data store not created eventhough IETF interface admin status is up.

Observation: Issue is because of tap interface details adding :0 in vpn config data store.
Example: port(tap) name created is : tapabcde-11. But, in VPN config data store it is adding tapabcde-11:0. Because of this mismatch VPN operational data store is not getting processed.

 Comments   
Comment by Deepthi V V [ 21/Jan/16 ]

https://git.opendaylight.org/gerrit/#/c/33221/:

Fix to ensure vpn interface is created with tap port name.

RCA: Vpn interface name and interface name should be same for the vpn interface configuration to be processed.

Comment by Deepthi V V [ 27/Jan/16 ]

Assigning to Raja to verify and close bug.

Comment by RajaRajan Manickam [ 29/Jan/16 ]

(In reply to Deepthi V V from comment #2)
> Assigning to Raja to verify and close bug.

VPN interface{operational) got created with the fix. So, closing this BUG.

Generated at Wed Feb 07 20:47:08 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.