kontainer-drivers.spec.ts is flaky

[mantis-toboggan-md]

There is a race condition in kontainer-drivers-spec.ts see run or run - the test activates two drivers using a bulk action, so they are downloaded and activated in parallel, but assertions against the state of the drivers happens sequentially.

[github-actions]

🎯 Agentic Issue Triage

Summary: The can activate drivers in bulk test in cypress/e2e/tests/pages/manager/kontainer-drivers.spec.ts is flaky due to a race condition. Two drivers (Oracle OKE and Open Telekom Cloud CCE) are bulk-activated in parallel, but the subsequent assertions check each driver's state sequentially — meaning the first assertion may time out waiting for a driver that is still downloading/activating.

Root Cause Analysis

Lines 145–152 of the spec show the problem:

cy.wait('`@activateOpenTelekomDriver`').its('response.statusCode').should('eq', 200);
cy.wait('`@activateOracleDriver`').its('response.statusCode').should('eq', 200);
// wait for drivers to be activating
driversPage.list().details(openTelekomDriver, 1).should('contain', 'Activating');
driversPage.list().details(oracleDriver, 1).should('contain', 'Activating');
// wait for drivers to be active
driversPage.list().details(openTelekomDriver, 1).should('contain', 'Active');
driversPage.list().details(oracleDriver, 1).should('contain', 'Active');

The two activate POST requests fire in parallel (bulk action), but assertions are sequential. By the time the first driver's Active state is confirmed, the second driver may have already passed through Activating and reached Active — or it may not have started yet, causing the Activating assertion to fail. The same pattern exists in can deactivate drivers in bulk (lines 299–308).

A previous fix for this issue existed for v2.13.x/v2.12.x (see #15764 / PR #15783/#15906), but the regression has reappeared on master/v2.15.0.

Suggested Fix

For the activate bulk test, skip the intermediate Activating assertion (it is a transient state and hard to reliably catch) and wait directly for Active on both drivers with an adequate timeout:

cy.wait(['`@activateOpenTelekomDriver`', '`@activateOracleDriver`']).then((interceptions) => {
  interceptions.forEach(({ response }) => expect(response?.statusCode).to.eq(200));
});
// Both drivers activate concurrently — wait for Active state with sufficient timeout
driversPage.list().details(openTelekomDriver, 1).should('contain', 'Active', { timeout: 120000 });
driversPage.list().details(oracleDriver, 1).should('contain', 'Active', { timeout: 120000 });

The same pattern should be applied to the deactivate bulk test.

Alternatively, assert that the state is either Activating or Active to make the intermediate check non-flaky:

driversPage.list().details(openTelekomDriver, 1).invoke('text').should('match', /Activating|Active/);

Reproduction / CI Failures

• Run 1
• Run 2

Look for assertion failures on the Activating state check for Oracle OKE or Open Telekom Cloud CCE.

Relevant Files

• cypress/e2e/tests/pages/manager/kontainer-drivers.spec.ts — the flaky spec (lines 100–161 for activate bulk, lines 283–317 for deactivate bulk)
• cypress/e2e/po/pages/cluster-manager/kontainer-drivers.po.ts — page object
• cypress/e2e/po/lists/kontainer-drivers-list.po.ts — list page object

Sub-tasks Checklist

• Fix the can activate drivers in bulk test to avoid flakiness on the Activating intermediate state assertion
• Fix the can deactivate drivers in bulk test with the same approach
• Review whether cy.wait(['@alias1', '@alias2']) can be used to wait for both intercepts in parallel
• Verify the fix locally or in CI before merging
• Consider whether similar patterns exist in other spec files (e.g. repositories.spec.ts)

Generated by Agentic Triage for issue #17735 · ● 247.8K · ◷

[github-actions]

🤖 Issue grooming questions

Thanks for the clear report and CI run links showing the flakiness! The problem statement, technical details (race condition identified in the test logic), and reproducibility are all present. One thing is needed before this can move to triage:

1. Missing: Acceptance Criteria

Please add a concrete, testable checklist defining what "fixed" looks like. For example:

• kontainer-drivers.spec.ts passes consistently without flakiness across multiple CI runs.
• The test correctly waits for both drivers to reach their activated state before asserting, regardless of parallelism.

This comment was generated automatically to help gather the information needed to groom this issue.

Generated by Daily Issue Grooming · ● 310.5K · ◷