This commit removes the workaround that switched tempest tenant isolation
to false if Neutron was enabled. Recent changes to both neutron and tempest
should make this safe finally.
Change-Id: I929fcc73a7ef9a10f01af422ff62f9d451d52ae3
| ... | ... |
@@ -266,11 +266,6 @@ function configure_tempest() {
|
| 266 | 266 |
|
| 267 | 267 |
# Compute |
| 268 | 268 |
iniset $TEMPEST_CONFIG compute change_password_available False |
| 269 |
- # Note(nati) current tempest don't create network for each tenant |
|
| 270 |
- # so reuse same tenant for now |
|
| 271 |
- if is_service_enabled neutron; then |
|
| 272 |
- TEMPEST_ALLOW_TENANT_ISOLATION=${TEMPEST_ALLOW_TENANT_ISOLATION:-False}
|
|
| 273 |
- fi |
|
| 274 | 269 |
iniset $TEMPEST_CONFIG compute allow_tenant_isolation ${TEMPEST_ALLOW_TENANT_ISOLATION:-True}
|
| 275 | 270 |
iniset $TEMPEST_CONFIG compute ssh_user ${DEFAULT_INSTANCE_USER:-cirros} # DEPRECATED
|
| 276 | 271 |
iniset $TEMPEST_CONFIG compute network_for_ssh $PRIVATE_NETWORK_NAME |