Pools created in lbaas context with admin tenant
Bug #1487061 reported by
eon
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Rally |
Fix Released
|
High
|
eon | ||
Bug Description
When using the lbaas context along with the network context the tenant_id of the created pools is the admin tenant. This causes issue later if we want to associate a VIP on the pool.
The tenant_id of the pool should be the same as the network.
| information type: | Public → Public Security |
| Changed in rally: | |
| importance: | Undecided → High |
| milestone: | none → 0.1.0 |
| information type: | Public Security → Private Security |
| information type: | Private Security → Public Security |
| Changed in rally: | |
| status: | New → In Progress |
| assignee: | nobody → eon (eon-5) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to rally (master) | #1 |
| Changed in rally: | |
| status: | In Progress → Fix Committed |
| Changed in rally: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit cff1ccc91adc854
Author: Jean-Philippe Braun <email address hidden>
Date: Thu Aug 20 16:17:01 2015 +0200
Create pool in lbaas context with correct tenant_id
When creating the pool in the lbaas context we use the same tenant_id
that was used to created the network on which the pool is created.
Change-Id: Ia06eddc7bd3fc3
Closes-Bug: #1487061
Signed-off-by: Jean-Philippe Braun <email address hidden>