-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errors in Deployability testing 4.9.0 alpha 3 #5616
Comments
Central component testing 🟢Centos-8YAML
Results
Running the installation command by hand
Amazon-2YAML
Result
Amazon-2: I have not been able to find a bug in the tests In relation to Centos-8 failure
The CentOS 8 reaching its end of life, the content from the CentOS 8 repositories has been moved to vault.centos.org. Please update your CentOS yum repository paths from 'mirror.centos.org' to 'vault.centos.org' to resolve the issue. Information from here and here However, the error message does look for the updated repository. @devops-team tried to replicate the error but it was not successful. Executing same YAML only testing Centos-8 Result
Amazon-2 and Centos-8: I have not been able to find a bug in the tests Anyway I have added 5 seconds of waiting to all the methods that perform port checking to give a safety margin to the check after install/stop/restart. |
Agent testing 🔴YAML
Result
The New executionResult
The following error message was found
|
Agent testing - New execution 🔴 -> 🟢Only windows-server2016 🟢YAML
Result
Windows-server-2016: I have not been able to find a bug in the tests Many hosts + windows-server2016 🔴YAML
Result
When running tests with more load, the reported error can be observed to repeat. I run smaller runs of Windows systems to see if the error persists. Testing manually, the commands , the environment and the installation works OK Adding a dynamic wait I could correctly handled this problem 🟢
|
Final results after fixes 🟢Central Components YAML
Agents YAML
By performing several tests, it has been proven that the port verification methods do not fail. |
LGTM |
UpdateFixes after review done |
Description
We have detected some failed tests in the Deployability testing issue in v4.9.0 alpha 3, we need to investigate it and check if is a test problem or create issues to other teams
Related
The text was updated successfully, but these errors were encountered: