No check that member address whether is in the member subnet

Bug #1585890 reported by dongjuan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
octavia
Invalid
Wishlist
Brandon Logan

Bug Description

issue is in kilo branch

member subnet cidr is 20.0.0.0/24, but member address is 30.0.0.11
but it configured ok.

[root@opencos2 v2(keystone_admin)]# neutron subnet-show 502be3ac-f8d8-43b3-af5b-f0feada72aed
+-------------------+--------------------------------------------+
| Field | Value |
+-------------------+--------------------------------------------+
| allocation_pools | {"start": "20.0.0.2", "end": "20.0.0.254"} |
| cidr | 20.0.0.0/24 |
| dns_nameservers | |
| enable_dhcp | True |
| gateway_ip | 20.0.0.1 |
| host_routes | |
| id | 502be3ac-f8d8-43b3-af5b-f0feada72aed |
| ip_version | 4 |
| ipv6_address_mode | |
| ipv6_ra_mode | |
| name | |
| network_id | 2e424980-14f0-4405-92dc-e4c57c32235a |
| subnetpool_id | |
| tenant_id | be58eaec789d44f296a65f96b944a9f5 |
+-------------------+--------------------------------------------+
[root@opencos2 v2(keystone_admin)]# neutron lbaas-member-create pool101 --subnet 502be3ac-f8d8-43b3-af5b-f0feada72aed --address 30.0.0.11 --protocol-port 80
Created a new member:
+----------------+--------------------------------------+
| Field | Value |
+----------------+--------------------------------------+
| address | 30.0.0.11 |
| admin_state_up | True |
| id | 1dccaaaa-2f00-4fd7-9a68-6031a96a172b |
| protocol_port | 80 |
| subnet_id | 502be3ac-f8d8-43b3-af5b-f0feada72aed |
| tenant_id | be58eaec789d44f296a65f96b944a9f5 |
| weight | 1 |
+----------------+--------------------------------------+

Tags: lbaas
Revision history for this message
Carl Baldwin (carl-baldwin) wrote :

Assigning for triage

Changed in neutron:
assignee: nobody → Brandon Logan (brandon-logan)
Changed in neutron:
status: New → Confirmed
importance: Undecided → Wishlist
Revision history for this message
Michael Johnson (johnsom) wrote :

This could be a valid use case where the address is accessible via a route on the specified subnet.

affects: neutron → octavia
Revision history for this message
Michael Johnson (johnsom) wrote :

Having members that are routable from a subnet is a valid use case. We should not limit that functionality. Marking this invalid.

Changed in octavia:
status: Confirmed → Invalid
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on neutron-lbaas (master)

Change abandoned by JingLiu (<email address hidden>) on branch: master
Review: https://review.openstack.org/408534

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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