Skip to content

Fix race condition: detect stale ProfileBundle status after CEL content update - #83

Open
taimurhafeez wants to merge 1 commit into
ComplianceAsCode:mainfrom
taimurhafeez:fix-waitForValidTestProfileBundles-after-celContentFile-update
Open

Fix race condition: detect stale ProfileBundle status after CEL content update#83
taimurhafeez wants to merge 1 commit into
ComplianceAsCode:mainfrom
taimurhafeez:fix-waitForValidTestProfileBundles-after-celContentFile-update

Conversation

@taimurhafeez

@taimurhafeez taimurhafeez commented Aug 13, 2026

Copy link
Copy Markdown
Collaborator

After ensureCELContentFile updates spec.celContentFile on the ocp4 ProfileBundle, waitForValidTestProfileBundles could immediately accept the stale VALID status from the initial XCCDF-only parse before the controller had time to re-parse with CEL content. This caused ValidateProfile to fail with "profile not found" for CEL-only profiles.

Track the ProfileBundle's resourceVersion after the spec update and require it to change before accepting VALID status, ensuring the controller has reconciled with the new CEL content file.

Reference PR where it was observed.
CI Job Result
Co-Authored-By: Claude Opus 4.6

@openshift-ci

openshift-ci Bot commented Aug 13, 2026

Copy link
Copy Markdown

@taimurhafeez: The following tests 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-aws-openshift-platform-compliance bede881 link true /test e2e-aws-openshift-platform-compliance
ci/prow/e2e-aws-ocp4-stig bede881 link true /test e2e-aws-ocp4-stig
ci/prow/e2e-aws-ocp4-cis bede881 link true /test e2e-aws-ocp4-cis
ci/prow/e2e-aws-rhcos4-moderate bede881 link true /test e2e-aws-rhcos4-moderate
ci/prow/e2e-aws-openshift-node-compliance bede881 link false /test e2e-aws-openshift-node-compliance

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.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant