Comment 15 for bug 1621798
Revision history for this message
| Timur Nurlygayanov (tnurlygayanov) wrote Re: More than15% of tempest tests triggers to an Error on CI | #15 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
The update:
We have manually deployed 4 different OpenStack configurations (the same configurations as we used before on CI) and manually started Tempest tests on these configurations. One configuration failed on OSTF check [2], 3 other configurations were deployed correctly and Tempest tests suite successfully passed for these configurations (results in TestRail for MOS 9.1 snapshot #266: [3][4][5]).
Short Summary:
One of the default OpenStack configurations failed OSTF tests [2], 2 other default configurations successfully passed Tempest test suite (summary pass rate 97%), the execution of Tempest on the one configuration is still in progress.
We need to investigate the failed deployment [2] and then restart Tempest tests for this configuration to make sure that we have the high pass rate for all required OpenStack configurations. We also need to wait when we execute Tempest on all default configuration to make sure we don't have any other issues.
I suggest we do not make HCF until the issue [2] will be investigated and fixed to make sure we don't have any important regression issues.
Note: QA team is working on the debugging and fixing of Tempest CI jobs to avoid any false-negative failures in the future. We will run Tempest test suite and upload results to TestRail manually every day while the CI jobs won't be fixed.
[1] https:/
[2] https:/
[3] https:/
[4] https:/
[5] https:/