Skip to content

Comments

e2e: fix admin credential lifecycle skip guard for integration/parallel#4161

Open
avollmer-redhat wants to merge 1 commit intomainfrom
fix-admin-cred-lifecycle-skip-guard
Open

e2e: fix admin credential lifecycle skip guard for integration/parallel#4161
avollmer-redhat wants to merge 1 commit intomainfrom
fix-admin-cred-lifecycle-skip-guard

Conversation

@avollmer-redhat
Copy link
Collaborator

@avollmer-redhat avollmer-redhat commented Feb 19, 2026

What

Commit d38165a introduced skip guards across three steps of the admin credential lifecycle test to work around ARO-23882 in the integration/parallel suite until 2026-03-11. However, the final skip guard (verifying that a newly-issued credential works post-revocation) was incorrectly gated on skipInt, a flag only set when the revocation wait loop itself times out.

Why

On the Feb 19 2026 run, credential revocation completed successfully for all three credentials within the 5-minute window, so skipInt remained false. The final skip guard therefore had no effect, and the test failed when the newly-issued credential returned 401 Unauthorized — the same underlying issue (ARO-23882 / OCPBUGS-62177) that the skip was meant to paper over.

Previous runs between Feb 12-18 happened to pass because at least one credential took longer than 5 minutes to revoke, setting skipInt=true accidentally triggering the skip. That is: the test was passing for the wrong reason.

Remove the skipInt && condition so the final skip guard mirrors the other two guards and unconditionally skips in integration/parallel until the deadline.

Commit d38165a introduced skip guards across three steps of the admin
credential lifecycle test to work around ARO-23882 in the
integration/parallel suite until 2026-03-11. However, the final skip
guard (verifying that a newly-issued credential works post-revocation)
was incorrectly gated on `skipInt`, a flag only set when the revocation
wait loop itself times out.

On the Feb 19 2026 run, credential revocation completed successfully for
all three credentials within the 5-minute window, so `skipInt` remained
false. The final skip guard therefore had no effect, and the test failed
when the newly-issued credential returned 401 Unauthorized — the same
underlying issue (ARO-23882 / OCPBUGS-62177) that the skip was meant to
paper over.

Previous runs between Feb 12-18 happened to pass because at least one
credential took longer than 5 minutes to revoke, setting `skipInt=true`
accidentally triggering the skip. That is: the test was passing for the
wrong reason.

Remove the `skipInt &&` condition so the final skip guard mirrors the
other two guards and unconditionally skips in integration/parallel until
the deadline.
@avollmer-redhat avollmer-redhat force-pushed the fix-admin-cred-lifecycle-skip-guard branch from 6a6eab9 to 661d925 Compare February 19, 2026 20:10
@openshift-ci
Copy link

openshift-ci bot commented Feb 19, 2026

@avollmer-redhat: 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-parallel 661d925 link true /test e2e-parallel

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.

@stevekuznetsov
Copy link
Contributor

/hold

We did NOT want to skip any other part of the test, that is on purpose. This is a novel and concerning issue unrelated to the original one.

Copy link
Collaborator

@miquelsi miquelsi left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci
Copy link

openshift-ci bot commented Feb 20, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: avollmer-redhat, miquelsi

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

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants