chore(e2e): re-enable bulk import tests on OSD

[PatAKnight]

Description

Attempts to re-enable the Bulk Import tests on OSD

Which issue(s) does this PR fix

• Fixes #?

PR acceptance criteria

Please make sure that the following steps are complete:

• GitHub Actions are completed and successful
• Unit Tests are updated and passing
• E2E Tests are updated and passing
• Documentation is updated if necessary (requirement for new features)
• Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer

[rhdh-qodo-merge]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🔒 No security concerns identified

⚡ Recommended focus areas for review

📚 Focus areas based on broader codebase context Test Stability The OSD-specific skip guard was removed, so these bulk import E2E tests will now run on osd-gcp jobs. Please confirm the underlying OSD failure condition is resolved, or replace the skip with a more targeted/temporary condition to avoid reintroducing known CI flakes. (Ref 1) test.describe.serial("Bulk Import plugin", () => { test.describe.configure({ retries: process.env.CI ? 5 : 0 }); Reference reasoning: Existing bulk import E2E coverage includes an explicit conditional skip for OSD jobs due to a tracked OSD environment issue. That pattern indicates the suite previously required environment-based gating to keep CI stable, so removing it should be validated against the same job matrix.

📄 References redhat-developer/rhdh/e2e-tests/playwright/e2e/plugins/bulk-import.spec.ts [284-351]

[rhdh-qodo-merge]

PR Type

Tests

---

Description

• Remove skip condition for bulk import tests on OSD

• Tests will now run on OSD GCP environment

• Resolves RHDHBUGS-555 blocking condition

---

File Walkthrough

	Relevant files
Tests	bulk-import.spec.ts Remove OSD skip condition from bulk import tests                  e2e-tests/playwright/e2e/plugins/bulk-import.spec.ts Removed test.skip() condition that was skipping tests on OSD GCP environment Tests previously blocked due to [RHDHBUGS-555](https://redhat.atlassian.net/browse/RHDHBUGS-555) will now execute +0/-4

---

[rhdh-qodo-merge]

PR Code Suggestions ✨

No code suggestions found for the PR.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Image was built and published successfully. It is available at:

• quay.io/rhdh-community/rhdh:pr-4504
• quay.io/rhdh-community/rhdh:pr-4504-a9f56d55

[PatAKnight]

/test e2e-osd-gcp-helm-nightly

[PatAKnight]

/test e2e-osd-gcp-helm-nightly

[PatAKnight]

/test e2e-osd-gcp-helm-nightly

[openshift-ci]

@PatAKnight: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-osd-gcp-helm-nightly	a9f56d5	link	false	/test e2e-osd-gcp-helm-nightly

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.