[NEUTRON-88] host-route option of NeutronSubnet not stored in MDSAL Created: 17/Dec/15  Updated: 30/Oct/17  Resolved: 30/Dec/15

Status: Resolved
Project: neutron
Component/s: transcriber
Affects Version/s: Multiple
Fix Version/s: None

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

Operating System: All
Platform: All

Issue Links:
Blocks
is blocked by NEUTRON-89 neutron-subnets.yang wrongly specifie... Resolved
External issue ID: 4805

 Description   

While creating a subnet user can specify a list of host-routes which specify a next-hop for different destination addresses. Code exists for it in neutron-spi and there is also attribute for it in neutron-subnet.yang, but this information is not stored in MDSAL.

Bug is in NeutronSubnetInterface.toMd() method where code to handle NeutronSubnet_HostRoutes is missing.

To reproduce:
1. If using devstack, use following to create subnet with host-route option:
neutron subnet-create --dns-nameserver 8.8.8.8 --host-route destination=1.1.1.0/24,nexthop=192.168.199.1 mynet1 192.168.199.0/24

2. If using postman/curl, use following json when creating subnet:
{
"subnet": {
"name": "",
"enable_dhcp": true,
"network_id": "e9330b1f-a2ef-4160-a991-169e56ab17f5",
"tenant_id": "4fd44f30292945e481c7b8a0c8908869",
"dns_nameservers": ["8.8.8.8"
],
"allocation_pools": [

{ "start": "192.168.199.2", "end": "192.168.199.254" }

],
"host_routes": [

{"nexthop": "192.168.199.1", "destination": "1.1.1.0/24"}

],
"ip_version": 4,
"gateway_ip": "192.168.199.1",
"cidr": "192.168.199.0/24",
"id": "3b80198d-4f7b-4f77-9ef5-774d54e17126"
}
}

 Comments   
Comment by Vishal Thapar [ 18/Dec/15 ]

Gerit review: https://git.opendaylight.org/gerrit/#/c/31579

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