We're seeing a 100% failure rate on the grenade multinode jobs on 2 cloud providers. We suspect it's because tempest is trying to ssh on the private network which it doesn't have access to. Lets revert to the previous behaviour and see if it fixes it
This reverts commit 46a272b31aaa2999b27c028a164f5548d8aad99b.
Change-Id: I50a6de8db7d74b2250a8ad166d13c39af37e1c6c
| ... | ... |
@@ -357,9 +357,6 @@ function configure_tempest {
|
| 357 | 357 |
iniset $TEMPEST_CONFIG compute flavor_ref $flavor_ref |
| 358 | 358 |
iniset $TEMPEST_CONFIG compute flavor_ref_alt $flavor_ref_alt |
| 359 | 359 |
iniset $TEMPEST_CONFIG compute ssh_connect_method $ssh_connect_method |
| 360 |
- # set the equiv validation option here as well to ensure they are |
|
| 361 |
- # in sync. They shouldn't be separate options. |
|
| 362 |
- iniset $TEMPEST_CONFIG validation connect_method $ssh_connect_method |
|
| 363 | 360 |
if [[ ! $(is_service_enabled n-cell) && ! $(is_service_enabled neutron) ]]; then |
| 364 | 361 |
iniset $TEMPEST_CONFIG compute fixed_network_name $PRIVATE_NETWORK_NAME |
| 365 | 362 |
fi |