Promote fips-scan to blocking for 5.0 nightly payloads - #82836
Promote fips-scan to blocking for 5.0 nightly payloads#82836redhat-chai-bot wants to merge 1 commit into
Conversation
|
[REHEARSALNOTIFIER] Note: If this PR includes changes to step registry files ( |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: redhat-chai-bot The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
💤 Files with no reviewable changes (2)
WalkthroughThe OCP 5.0 release configurations now require the ChangesFIPS scan requirement
Estimated code review effort: 1 (Trivial) | ~2 minutes 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This PR removes
optional: truefrom thefips-scanverify job entry in the 5.0 release controller configs, re-promoting it from informing to blocking (qualifying).\n\nThe job was temporarily demoted to informing in #80487 due to a known RHCOS 10 issue. This change restores it as a blocking job for 5.0 nightly payloads.\n\n## Changes\n\n-core-services/release-controller/_releases/release-ocp-5.0.json: removed\"optional\": truefromfips-scan\n-core-services/release-controller/_releases/priv/release-ocp-5.0.json: removed\"optional\": truefromfips-scanAI-generated. Review for accuracy.
@neisw requested via Chai Bot
Summary by CodeRabbit
The PR makes the
fips-scanverification job blocking for 5.0 nightly payloads in both release controller configurations. This restores the job’s qualifying status after its earlier demotion for the known RHCOS 10 issue. Its disabled status, retry limit, and Prow configuration remain unchanged.