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

[ENHANCEMENT] Enable QA To Create the Helm Chart with OpenSearch via GHA #2626

Open
3 tasks
Tracked by #2774
slolatte opened this issue Dec 2, 2024 · 7 comments
Open
3 tasks
Tracked by #2774
Assignees
Labels
area/ci kind/enhancement New feature or request

Comments

@slolatte
Copy link

slolatte commented Dec 2, 2024

Describe the use case:

I am currently working on expanding the cross component test suite to cover OpenSearch. For context, please see the following ticket. However, I am running into some Helm Chart installation errors. I have followed the setup instructions in our documentation, and using the OpenSearch instance provided by infra.

Describe the enhancement/feature:

For more context, please see the following Slack thread.

Desired outcome and acceptance tests:

This will enable QA on a nightly basis and during release time, to test OpenSearch.

Tasks

Preview Give feedback
  1. hamza-m-masood
  2. area/ci tool/github-actions version/8.6
    hamza-m-masood
@slolatte slolatte added the kind/enhancement New feature or request label Dec 2, 2024
@hamza-m-masood hamza-m-masood added the kind/medic Tasks for the medic label Jan 6, 2025
@hamza-m-masood hamza-m-masood self-assigned this Jan 6, 2025
@hamza-m-masood
Copy link
Contributor

I will create an OpenSearch instance for QA team to use. The database must be wiped via a github actions workflow before every nightly run.

@hamza-m-masood
Copy link
Contributor

OpenSearch instance is now created.
I will work on modifying the github actions workflow now.

@hamza-m-masood
Copy link
Contributor

Please note: This github action workflow can only be run alone. It will not be possible to run many instances of this github action at the same time because the DB would need to be wiped before every run.

@hamza-m-masood
Copy link
Contributor

I can trigger a run from the e2e QA repo with the correct values.yaml so the platform uses OpenSearch as a DB. The problem that I have just discovered is that our integration tests are not built to support DBs other than elasticsearch. I see that two pre-flight tests are failing because of the missing elasticsearch pods:

  1. TEST-Liveness
  2. TEST-Readiness

The core test suite will probably have more failing tests, but I can only see that when I fix the pre-flight tests.

Another PR must be created to fix these integration tests and support other databases.

@slolatte
Copy link
Author

@hamza-m-masood Thanks for the update and for the support with this!

@hamza-m-masood
Copy link
Contributor

PR created: #2764
It is a WIP

@hisImminence
Copy link
Contributor

Removing the medic label as this is no medic task anymore but a prioritized issue.

@hisImminence hisImminence removed the kind/medic Tasks for the medic label Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ci kind/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants