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

Run Operator tests with the latest Manager before release #4030

Open
mikliapko opened this issue Sep 11, 2024 · 3 comments
Open

Run Operator tests with the latest Manager before release #4030

mikliapko opened this issue Sep 11, 2024 · 3 comments
Assignees
Labels
qa should be used for qa team testing tasks

Comments

@mikliapko
Copy link

Operator test suite - https://github.com/scylladb/scylla-operator/tree/master/test/e2e/set

The suite can be run with a different manager version by sending a dummy PR updating the manager and manager agent image tags (like here scylladb/scylla-operator#2089 or here scylladb/scylla-operator#2105).

Also, we need to investigate whether available Operator SCT tests are able to discovery recently found Manager regression issues: #4028 and #3989

@mikliapko mikliapko added the qa should be used for qa team testing tasks label Sep 11, 2024
@mikliapko mikliapko self-assigned this Sep 11, 2024
@karol-kokoszka
Copy link
Collaborator

The regression with Scylla Manager that was found by Operator tests came from Operator repo tests, not from SCT.
The best would be to have possibility of integrating with what they have in their repo.

cc: @zimnx @tnozicka

@tnozicka
Copy link
Member

I am planing to setup "latest" integration jobs between the projects (now that we have the unified config).

@tnozicka
Copy link
Member

scylladb/scylla-operator#1611
(there can be other variants when its configurable with the first job)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
qa should be used for qa team testing tasks
Projects
None yet
Development

No branches or pull requests

3 participants