Skip to content

Fix tests for CI #1108

Merged
openshift-merge-bot[bot] merged 4 commits intoredhat-developer:v1.20from
trdoyle81:fix-ci-v120-only
Mar 31, 2026
Merged

Fix tests for CI #1108
openshift-merge-bot[bot] merged 4 commits intoredhat-developer:v1.20from
trdoyle81:fix-ci-v120-only

Conversation

@trdoyle81
Copy link
Copy Markdown
Member

What type of PR is this?
/kind failing-test

What does this PR do / why we need it:
This PR fix two E2E test failures that happen when running v1.20 tests against OpenShift 4.21 in CI:

  • **Parallel Fix (1-050_validate_sso):**o skip the OIDC status check when a .ci version string is detected in the OpenShift version.
  • Sequential Fix (1-108_alternate_cluster_roles): Fix a race condition in the AfterEach cleanup block. The test was failing with a 404 NotFound error when trying to delete the test-gitops-ns namespace because it had already been deleted during the test execution. T

Have you updated the necessary documentation?

  • Documentation update is not required by this PR.

Which issue(s) this PR fixes:

Fixes #

Test acceptance criteria:

  • E2E Test

How to test changes / Special notes to the reviewer:

  1. The parallel failure was explicitly caused by the test logic incorrectly parsing the server version 4.21.0-0.ci...
  2. The sequential failure was a race condition. The 404 status error and Reason: "NotFound" for the test-gitops-ns namespace in the AfterEach stack trace.

Signed-off-by: Triona Doyle <bot@example.com>
@openshift-ci openshift-ci bot added the kind/failing-test Categorizes issue or PR as related to a frequently failing test. label Mar 30, 2026
@openshift-ci openshift-ci bot requested review from chetan-rns and jannfis March 30, 2026 11:36
@trdoyle81 trdoyle81 requested a review from varshab1210 March 30, 2026 11:49

// also skip for CI
if strings.Contains(ocVersion, ".ci") {
Skip("skipping this test in CI because OIDC is not enabled by default")
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@trdoyle81 if the test was succeeding on 4.21 while testing 1.20 RC I don't think it should be skipped in CI

Copy link
Copy Markdown
Member Author

@trdoyle81 trdoyle81 Mar 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

auth operator on 4.21 seems to be way more picky about certificates than 4.20 was. So on any cluster that doesn't have genuine ingress certs the operator is staying stuck in progressing. I'm seeing this fail on standard 4.21 clusters too and not just in prow so I think we actually might need to skip this test for 4.21 entirely ?

Copy link
Copy Markdown
Member

@varshab1210 varshab1210 Mar 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Never mind, I didn't realise this test was modified. Can we add a check to skip in CI+ if its version is < 4.20?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done. Updated to skip > 4.20. Also updated the AfterEach with null check because the namespace won't exist on skip.

@varshab1210
Copy link
Copy Markdown
Member

/lgtm

Signed-off-by: Triona Doyle <bot@example.com>
@openshift-ci openshift-ci bot removed the lgtm label Mar 30, 2026
Signed-off-by: Triona Doyle <bot@example.com>
Signed-off-by: Triona Doyle <bot@example.com>
@varshab1210
Copy link
Copy Markdown
Member

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm label Mar 31, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci bot commented Mar 31, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: varshab1210

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit 74ae851 into redhat-developer:v1.20 Mar 31, 2026
5 checks passed
@trdoyle81
Copy link
Copy Markdown
Member Author

/cherry-pick master

@openshift-cherrypick-robot
Copy link
Copy Markdown

@trdoyle81: only redhat-developer org members may request cherry picks. If you are already part of the org, make sure to change your membership to public. Otherwise you can still do the cherry-pick manually.

Details

In response to this:

/cherry-pick master

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.

@trdoyle81
Copy link
Copy Markdown
Member Author

/cherry-pick master

@openshift-cherrypick-robot
Copy link
Copy Markdown

@trdoyle81: #1108 failed to apply on top of branch "master":

Applying: Fix tests for CI
Using index info to reconstruct a base tree...
M	test/openshift/e2e/ginkgo/parallel/1-050_validate_sso_test.go
M	test/openshift/e2e/ginkgo/sequential/1-108_alternate_cluster_roles_cluster_scoped_instance_test.go
Falling back to patching base and 3-way merge...
Auto-merging test/openshift/e2e/ginkgo/sequential/1-108_alternate_cluster_roles_cluster_scoped_instance_test.go
CONFLICT (content): Merge conflict in test/openshift/e2e/ginkgo/sequential/1-108_alternate_cluster_roles_cluster_scoped_instance_test.go
Auto-merging test/openshift/e2e/ginkgo/parallel/1-050_validate_sso_test.go
CONFLICT (content): Merge conflict in test/openshift/e2e/ginkgo/parallel/1-050_validate_sso_test.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 Fix tests for CI

Details

In response to this:

/cherry-pick master

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved kind/failing-test Categorizes issue or PR as related to a frequently failing test. lgtm

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants