Octavia-dashboard incorrectly requires subnet-id for members

Bug #2040653 reported by Ed Fisher
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
octavia
Confirmed
Medium
Unassigned

Bug Description

The dashboard has two undesirable behaviors when adding members to a pool on an amphora loadbalancer:

- You cannot add an external member unless you select a subnet it's accessible from. This isn't required via the API, and should either be prefilled with the subnet of the loadbalancer's vip or not be required.
- Members added via the list of servers are copied including their subnet ID, and the subnet ID can't be changed before the pool is updated. Users should be able to, again, leave the subnet blank.

The latter case can result in an amphora in AZ1 being assigned an IP address only available in AZ2, which will break connectivity to the member.

Revision history for this message
Gregory Thiemonge (gthiemonge) wrote :

Thanks for reporting it,
I confirm both issues

Changed in octavia:
importance: Undecided → Medium
status: New → Confirmed
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.