[CONTROLLER-1042] "subnet_id" attribute missing in NeutronLoadBalancerPoolNorthbound Created: 24/Nov/14  Updated: 25/Jul/23  Resolved: 04/May/15

Status: Resolved
Project: controller
Component/s: adsal
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Shreshtha Joshi Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 2426

 Description   

As per OpenStack Networking (neutron) API v2.0, "subnet_id" is an attribute of LoadBalancerPool, whereas in ODL it is an attribute of member of the pool (NeutronLoadBalancerPoolMembersNorthbound).

Creating LoadBalancerPool through openstack UI
openstack will provide a subnet_id while creating a LoadBalancerPool.
whereas, when LoadBalancerPool creation call reaches ODL, the NeutronLoadBalancerPool object does not have "subnet_id" as an attribute which can be mapped to the one supplied by openstack.

 Comments   
Comment by Srini Seetharaman [ 25/Nov/14 ]

This is not true from the API listed here for 2.0:
http://developer.openstack.org/api-ref-guides/bk-api-ref-networking-v2.pdf

Comment by Shreshtha Joshi [ 08/Dec/14 ]

In OpenStack Networking (neutron) API v2.0 Reference (http://developer.openstack.org/api-ref-guides/bk-api-ref-networking-v2.pdf), "subnet_id" is also a part of pool.

Also, both openstack UI and CLI command to create a pool it takes subnet_id as a must parameter, whereas the same is not required to create a member.

Comment by Carol Sanders [ 04/May/15 ]

This bug is part of the project to Move all ADSAL associated component bugs to ADSAL

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