lbaas security group
Bug #1295424 reported by
Kevin Fox
This bug affects 14 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
octavia |
Expired
|
Low
|
Unassigned |
Bug Description
There seems to be no way of specifying which security group a lbaas vip gets. It looks to default to 'default' in Havana. When you place a load balancer on a backend private neutron network, it gets the security group member rules from 'default' which are for the wrong subnet.
Manually drilling down to find the port neutron port id, and then fixing the security_group on the vip port does seem to work.
There needs to be a way to specify the security groups when you create the vip.
Changed in neutron: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
importance: | Wishlist → Low |
tags: | added: lbaas |
Changed in neutron: | |
assignee: | nobody → Jaume Devesa (devvesa) |
tags: | added: api |
Changed in neutron: | |
status: | Triaged → In Progress |
Changed in neutron: | |
assignee: | Jaume Devesa (devvesa) → nobody |
status: | In Progress → Incomplete |
Changed in neutron: | |
assignee: | nobody → Tyler Britten (9-me-9) |
Changed in neutron: | |
assignee: | Tyler Britten (9-me-9) → nobody |
affects: | neutron → octavia |
To post a comment you must log in.
Affects https:/ /bugs.launchpad .net/heat/ +bug/1295425