Once the nova patch series that converts from the nova-consoleauth
backend -> cell database backend lands, we can re-enable the novnc
tests in tempest.
Depends-On: If1b6e5f20d2ea82d94f5f0550f13189fc9bc16c4
Change-Id: I2939191a1c3ce49fa2104b4ffdf795fc416a1c33
... | ... |
@@ -386,14 +386,7 @@ function configure_tempest { |
386 | 386 |
iniset $TEMPEST_CONFIG compute-feature-enabled volume_multiattach True |
387 | 387 |
fi |
388 | 388 |
|
389 |
- # TODO(melwitt): If we're running per-cell console proxies, the novnc tests |
|
390 |
- # won't work until the nova patch series lands that converts from the |
|
391 |
- # nova-consoleauth backend -> cell database backend. So disable them unless |
|
392 |
- # we're running Cells v1. Cells v1 will never support the cell database |
|
393 |
- # backend, so it will always run with a global nova-consoleauth. |
|
394 |
- # Once the patch that converts from the nova-consoleauth backend -> cell |
|
395 |
- # database backend lands, we can re-enable the novnc tests for Cells v2. |
|
396 |
- if is_service_enabled n-novnc && is_service_enabled n-cell; then |
|
389 |
+ if is_service_enabled n-novnc; then |
|
397 | 390 |
iniset $TEMPEST_CONFIG compute-feature-enabled vnc_console True |
398 | 391 |
fi |
399 | 392 |
|