e3405ba808
Due to issue described in related bug report, it seems that it may happen sometimes that tempest will start trying to ssh to the instance before ssh key will be really configured in the instance and in such case it may happened that there will be AuthenticationFailure error always there. Even if ssh key will be configured properly later during the test. To workaround that issue and avoid failures of tests, this patch adds check if the vm is really booted and ready to ssh. It is done by checking console log of the VM and looking for specific string "login:" which appears at least in case of Cirros and Ubuntu images used in our CI jobs. In case when such string will not be found, test will continue to run and will still try to ssh to the instance. So in worst case it may slow ssh to the instance a bit but shouldn't really have any bad impact on test as before this patch it would probably also wait similar amount of time but on trying to SSH to the instance. Similar workaround was introduced in the neutron-tempest-plugin with [1]. After it was merged number of failed jobs due to ssh "Authentication failure" issues lower down significantly. [1] https://review.opendev.org/#/c/758968/ Change-Id: I84a7c2fc389d181388ef821848ffad4bc67f1213 Related-Bug: #1892861 |
||
|---|---|---|
| .. | ||
| utils | ||
| __init__.py | ||
| compute.py | ||
| credentials_factory.py | ||
| custom_matchers.py | ||
| identity.py | ||
| image.py | ||
| tempest_fixtures.py | ||
| waiters.py | ||