+++ This bug was initially created as a clone of Bug #1920163 +++ Description of problem: There is a bug in the function wait_for_guest_os_ready which we hit when running neutron tempest tests while tempest config compute_feature_enabled.console_output set to False. With console_output set to True we do not hit the bug but test execution is very slow for tests where we launch more than 1 VM because each VM is spawned after previous one is fully booted. this causes that some downstream multicast tests which are spawning 3+ VMs are very slow. Note: with console_output set to False we are able to launch all 3-5 VMs simultaneously. All VMs are up after less than a minute. Version-Release number of selected component (if applicable): python3-neutron-tests-tempest-0.9.0-2.20210224125007.15c85f6.el8ost.1.noarch How reproducible: 100% Steps to Reproduce: 1. Set tempest config value compute_feature_enabled.console_output to False 2. Run any test that uses wait_for_guest_os_ready, e.g. test_multicast_between_vms_on_same_network Actual results: Test fails on wrong index Expected results: Test passes
Verified on puddle RHOS-16.2-RHEL-8-20210728.n.2 with python3-neutron-tests-tempest-0.9.0-2.20210528123644.el8ost.2.noarch. Verified that it is possible to run tempest with console_output = False without errors.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat OpenStack Platform (RHOSP) 16.2 enhancement advisory), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2021:3483