[BUGFIX] Add e2e test for file-storage multi-replica dashboard sync#411
Open
slashpai wants to merge 1 commit into
Open
[BUGFIX] Add e2e test for file-storage multi-replica dashboard sync#411slashpai wants to merge 1 commit into
slashpai wants to merge 1 commit into
Conversation
slashpai
changed the title
1 task
slashpai
force-pushed
the
triage
branch
2 times, most recently
from
fab522b to
471788d
Compare
rickardsjp
reviewed
Jun 1, 2026
Contributor
rickardsjp
left a comment
rickardsjp
left a comment
There was a problem hiding this comment.
I'm a little surprised the test passes, which indicates that it might be flaky. However, I'm unfamiliar with kuttle and you might know better. Looking at the KEP, they write:
A failure of a previous command will restart the loop of commands (meaning command 2 will not be executed unless command 1 succeeds)
I wonder if there are additional reconciliations happening and the nature of the restarts means that eventually the operator gets the other replica. As it stands, this test doesn't seem to correspond to the behavior of a manual test in a kind cluster as described in #409.
Member
Author
|
I am working on rewriting test. |
slashpai
force-pushed
the
triage
branch
2 times, most recently
from
c518239 to
892854e
Compare
Add Kuttl test replica-file-sync that deploys Perses with file DB and three StatefulSet replicas, then asserts the dashboard exists on each pod via direct port-forward (not only through the ClusterIP Service). Related-to: perses#409 Signed-off-by: Jayapriya Pai <janantha@redhat.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add Kuttl test replica-file-sync that deploys Perses with file DB and three StatefulSet replicas, then asserts the dashboard exists on each pod via direct port-forward (not only through the ClusterIP Service).
Related-to: #409, #412
Description
Closes: #ISSUE-NUMBER
Type of change
FEATURE(non-breaking change which adds functionality)ENHANCEMENT(non-breaking change which improves existing functionality)BUGFIX(non-breaking change which fixes an issue)BREAKINGCHANGE(fix or feature that would cause existing functionality to not work as expected)DOC(documentation only)IGNORE(tooling, build system, CI, etc.)Verification
Checklist