Context
We regularly have errors reported on install or upgrade that a table such as RUCSS or ATF already exists (for instance #54, see also on Slack, we have many examples).
Those errors can occur because multiple requests try to create/update the table after an install/update; this is not an issue.
Expected behavior
Rocket-E2E tests must not fail only because there are error logs related to "table already exists" in the error log file.
Acceptance Criteria
Run smoke E2E tests multiple times until this error occurs in the logs. The related test must not fail because of this.
Additional information
The other possibility I can think of is to prevent the error from happening in the first place. This would require a lock mechanism, which I think is risky and probably overkill for this.
MathieuLamiot
commented
2 months ago
Context We regularly have errors reported on install or upgrade that a table such as RUCSS or ATF already exists (for instance #54, see also on Slack, we have many examples). Those errors can occur because multiple requests try to create/update the table after an install/update; this is not an issue.
Expected behavior
Acceptance Criteria Run smoke E2E tests multiple times until this error occurs in the logs. The related test must not fail because of this.
Additional information The other possibility I can think of is to prevent the error from happening in the first place. This would require a lock mechanism, which I think is risky and probably overkill for this.