[RELEASE] Release version 2.4.1 #2925
Comments
github-actions
bot
added
release
untriaged
This was referenced Dec 6, 2022
Merged
Release testingWe have release candidates built and ready for testing. OpenSearch docker
OpenSearch-Dashboards docker
Use below artifacts to deploy OpenSearch and OpenSearch Dashboards on different platforms |
|
Integration tests for Linux are failing for below components:
|
|
SQL below are the logs for windows: failure log
|
|
Also windows integ test failing for asynchronous-search without security: failure log``` 2022-12-08 22:33:41 INFO =============================================== 2022-12-08 22:33:41 INFO Running integration tests for asynchronous-search 2022-12-08 22:33:41 INFO =============================================== 2022-12-08 22:33:41 INFO Executing "bash C:\Users\Administrator\opensearch-build\scripts\default\integtest.sh -b localhost -p 9200 -s false -v 2.4.1" in C:\Users\ADMINI~1\AppData\Local\Temp\2\tmppcxig_tl\asynchronous-search 2022-12-08 22:37:36 INFO Recording component test results for asynchronous-search at C:\Users\Administrator\opensearch-build\test-results\3456\integ-test\asynchronous-search\without-security\test-results 2022-12-08 22:37:36 INFO Integration test run failed for component asynchronous-search 2022-12-08 22:37:36 INFO OpenJDK 64-Bit Server VM warning: Ignoring option --illegal-access=warn; support was removed in 17.0 REPRODUCE WITH: gradlew ':integTest' --tests "org.opensearch.search.asynchronous.restIT.AsynchronousSearchRestIT.testGetWithKeepAliveUpdate" -Dtests.seed=EBCF501A714D591A -Dtests.security.manager=false -Dtests.locale=hi-IN -Dtests.timezone=Asia/Vientiane -Druntime.java=17 Suite: Test class org.opensearch.search.asynchronous.restIT.AsynchronousSearchRestIT 75 tests completed, 1 failed === Standard output of node === Standard error of node FAILURE: Build failed with an exception.
BUILD FAILED in 3m 54s 2022-12-08 22:37:36 INFO Sending SIGKILL to PID 7992 2022-12-08 22:45:33 INFO =============================================== REPRODUCE WITH: gradlew ':notifications:integTest' --tests "org.opensearch.integtest.config.DeleteNotificationConfigIT.test Delete some items from multiple notification config with missing configs should fail" -Dtests.seed=E1F5A8212A0E06CE -Dtests.security.manager=false -Dtests.locale=nb -Dtests.timezone=America/Cayenne -Druntime.java=17 Suite: Test class org.opensearch.integtest.config.DeleteNotificationConfigIT 75 tests completed, 1 failed === Standard output of node === Standard error of node FAILURE: Build failed with an exception.
BUILD FAILED in 4m 24s |
|
Notifications is failing for both with and without security for windows as well: failure log``` 2022-12-08 22:50:29 INFO =============================================== 2022-12-08 22:50:29 INFO Running integration tests for notifications 2022-12-08 22:50:29 INFO =============================================== 2022-12-08 22:50:29 INFO Executing "bash C:\Users\Administrator\opensearch-build\scripts\default\integtest.sh -b localhost -p 9200 -s false -v 2.4.1" in C:\Users\ADMINI~1\AppData\Local\Temp\2\tmpyfl4acc0\notifications\notifications 2022-12-08 22:53:01 INFO Recording component test results for notifications at C:\Users\Administrator\opensearch-build\test-results\3455\integ-test\notifications\without-security\test-results 2022-12-08 22:53:01 INFO Integration test run failed for component notifications 2022-12-08 22:53:01 INFO OpenJDK 64-Bit Server VM warning: Ignoring option --illegal-access=warn; support was removed in 17.0 REPRODUCE WITH: gradlew ':notifications:integTest' --tests "org.opensearch.integtest.config.DeleteNotificationConfigIT.test Delete some items from multiple notification config with missing configs should fail" -Dtests.seed=F363E8B88C588A4C -Dtests.security.manager=false -Dtests.locale=en -Dtests.timezone=Europe/Athens -Druntime.java=17 REPRODUCE WITH: gradlew ':notifications:integTest' --tests "org.opensearch.integtest.config.DeleteNotificationConfigIT.test Delete partial items from multiple notification config" -Dtests.seed=F363E8B88C588A4C -Dtests.security.manager=false -Dtests.locale=en -Dtests.timezone=Europe/Athens -Druntime.java=17 Suite: Test class org.opensearch.integtest.config.DeleteNotificationConfigIT 61 tests completed, 2 failed === Standard output of node === Standard error of node FAILURE: Build failed with an exception.
BUILD FAILED in 2m 30s 2022-12-08 22:53:01 INFO Sending SIGKILL to PID 9788 |
|
Security Anaylatics is failing for windows both with and without security: failure log
|
|
@gaiksaya The Notifications failure is the backend flaky test issue due to a race condition on searchable documents that I mentioned before. The fix for this is being tracked in opensearch-project/notifications#381 and it's a known issue. We can sign off on Notifications if that's the only failures you saw. |
|
OpenSearch Dashboards Windows integration test results: With security:Failing components:
failure log
|
|
OpenSearch Dashboards Windows integration test results: Without security:Failing components:
failure log
|
|
The test that failed for the |
|
Verified on windows platform w/o security plugin, and we can sign off for Gantt Charts, observability-dashboards, Query Workbench Dashboards. The failing tests for Gantt Charts and Query Workbench Dashboards are flaky, for observability-dashboards, some of them are failing because they are not yet updated for 2.4. We had a pending PR to update tests in FTR but not yet being merge in. That PR is to address flaky/failing tests, and we are working on getting it merge in soon. |
5 tasks
|
Index Management with security: failure log
The test passed successfully for Index Management without security. Thanks! |
|
SQL plugin required additional config . After adding the config the tests were successful for on all platforms. |
|
Security-Analytics fix for successful integration tests on windows. opensearch-project/security-analytics#176 |
|
Index-Management security test cases failing due to the test framework's defect. We create this issue to track and fix it. |
|
Security Analytics found an issue in OpenSearch Release Candidate. Due to this, we are rebuilding RC again. Thanks! |
|
New build was successful: https://build.ci.opensearch.org/job/distribution-build-opensearch/6698/ |
This was referenced Dec 13, 2022
|
Able to install native plugins: |
|
Signature looks good: |
|
verified docker and yum installation, everything working as expected. |
|
We have released 2.4.1 successfully 🎉 |
|
All the post release tasks are completed. Closing this issue. Thanks! |
|
@qreshi Notifications : opensearch-project/notifications#381 Can you tag the issues that being tracked for flaky tests with next release (possibly 2.5.0) so that they get resolved by then. |
|
At times, release date changes towards the end of the release. With release notes are created during pre-release stage, there are chances that release date in notes is not correct. With 1.3.7 & 2.4.1 we identify that s/w release date slipped but the release date in the release notes wasn't. I propose to add one verification step inside 1.3.7 Release Notes: opensearch-project/OpenSearch#5536 |
|
Hi @dreamer-89 , Now that I think about it, even if there is a verify release date check, the release date can still be changed after the code cut off date. That means the particular release tag won't be updated with recent changes. Is removing the release date from release notes an option here? |
Thanks @gaiksaya for your inputs.
I think this is what this verification solves here. When release launch slips, verify release date is correct in release notes. If
I am open to this option and we can discuss more here. Not sure how is this date consumed today. |
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Release OpenSearch and OpenSearch Dashboards 2.4.1
I noticed that a manifest was automatically created in manifests/2.4.1. Please follow the following checklist to make a release.
How to use this issue
This Release Issue
This issue captures the state of the OpenSearch release, its assignee is responsible for driving the release. Please contact them or @mention them on this issue for help. There are linked issues on components of the release where individual components can be tracked. More details are included in the Maintainers Release owner section.
Release Steps
There are several steps to the release process, these steps are completed as the whole release and components that are behind present risk to the release. The release owner completes the tasks in this ticket, whereas component owners resolve tasks on their ticket in their repositories.
Steps have completion dates for coordinating efforts between the components of a release; components can start as soon as they are ready far in advance of a future release.
Component List
To aid in understanding the state of the release there is a table with status indicating each component state. This is updated based on the status of the component issues.
Preparation
Update the Campaigns section to include monitoring campaigns during this release.__REPLACE_RELEASE-__placeholders have actual dates.Create a release issue in every component repo that links back to this issue, update Components section with these links.Ensure that all release issues created above are assigned to an owner in the component team.CI/CD (Feature Freeze) - _Ends Dec 07, 2022
<MajorVersion>.<MinorVersion>early.Campaigns
REPLACE with OpenSearch wide initiatives to improve quality and consistency.
Code Complete - Ends Dec 07, 2022
Release testing - _Ends Dec 12, 2022
<MajorVersion>.<MinorVersion>for the release.Performance testing validation - Ends REPLACE_RELEASE-minus-6-days
Performance tests do not show a regressionLongevity tests do not show any issuesRelease - Ends Dec 13, 2022
v2.4.1in all projects have been resolved.Post Release
2.4.1release.2.4.1release.Components
Replace with links to all component tracking issues.
Legend
The text was updated successfully, but these errors were encountered: