-
Notifications
You must be signed in to change notification settings - Fork 281
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
[AUTOCUT] Integration Test failed for security: 2.12.0 tar distribution #3876
Comments
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
@peternied I've seen these issues happen due to the new demo configuration script changes. Let me look into this/how to fix it. |
@reta for this one, you have to now pass in the OPENSEARCH_INITIAL_ADMIN_PASSWORD= strong password. Then it should work. Pending merging of this PR: opensearch-project/opensearch-build#4274, the error message will be more clear. |
@reta The docker compose file has changed a bit to adapt to the new password changes. 2.12 now requires admin password to be passed in order to spin up cluster. The opensearch-project/opensearch-build#4274 address the changes required to spin-up docker cluster. An easy option to pass custom password is by creating a I agree with @derek-ho 's suggestion to pass the custom password by setting the variable in order to fix the problem. Expand to see logs:
|
@derek-ho @DarshitChanpura We need to update the Docker image guidelines (both on Docker Hub and in the documentation) since the containers could not be used out of the box anymore. It also affects projects that use Docker based integration testing (Testcontainers or |
[Triage] This issue is related to the admin:admin changes being partially supported at the moment causing the early distributions to fail some tests. This will be addressed with the remaining admin:admin tasks. |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
The integration test failed at distribution level for component security |
@derek-ho I looked at the failed test run
Hacky way to get this log
|
@peternied The scenario presented in error logs would happen when opensearch.yml already has See this blob which writes the setting to opensearch.yml:
Do you know if there is a way we can check the pre and post state of opensearch.yml when executing demo config install script. |
Closing the issue as the Integration Test passed for security |
The integration test failed at distribution level for component security
Version: 2.12.0
Distribution: tar
Architecture: arm64
Platform: linux
Please check the logs: https://build.ci.opensearch.org/job/integ-test/6700/display/redirect
* Test-report manifest:*
- https://ci.opensearch.org/ci/dbc/integ-test/2.12.0/9061/linux/arm64/tar/test-results/6700/integ-test/test-report.yml
Note: Steps to reproduce, additional logs and other files can be found within the above test-report manifest.
Instructions of this test-report manifest can be found here.
The text was updated successfully, but these errors were encountered: