Skip to content
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

[FEATURE] Run integration tests as part of the OpenSearch distribution #198

Open
Tracked by #58
dblock opened this issue Apr 27, 2022 · 2 comments
Open
Tracked by #58
Labels
ci enhancement New feature or request Priority-Low

Comments

@dblock
Copy link
Member

dblock commented Apr 27, 2022

Is your feature request related to a problem?
Following opensearch-project/opensearch-build#2043 and coming from opensearch-project/opensearch-build#58 there's no automated testing that PA works as part of the OpenSearch distribution.

What solution would you like?
Run integration tests as part of the distribution.

@dblock dblock added enhancement New feature or request untriaged labels Apr 27, 2022
@dblock dblock changed the title [FEATURE] Run integration tests as part of the distribution [FEATURE] Run integration tests as part of the OpenSearch distribution Apr 27, 2022
@dblock dblock added the v2.1.0 label Apr 27, 2022
@sruti1312
Copy link
Contributor

sruti1312 commented May 3, 2022

PA spins up a docker (with OpenSearch docker artifacts), installs PA plugin, starts the PA reader process and runs a bunch of integration tests as a part of CI run (using custom Dockerfile).

Currently there are no tests that run as a part of tar/ rpm distribution as framework. For PA integration tests to work on tar/ rpm distribution it requires spinning up this PA reader process. As of now integTest framework supports spinning up tar/rpm cluster without PA process and does not support starting separate processes.

Opened an issue on OpenSearch to track adding this functionality to the integration framework.
opensearch-project/OpenSearch#3162

@kkhatua
Copy link
Member

kkhatua commented Jan 5, 2023

Removing the untriaged label and marking as low Priority-Low since there is a need for the integ framework to support spinning up a standalone process (i.e. the Reader process).

@kkhatua kkhatua removed the untriaged label Jan 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci enhancement New feature or request Priority-Low
Projects
None yet
Development

No branches or pull requests

4 participants