-
Bug
-
Resolution: Done
-
Critical
-
None
-
ACM 2.15.0
-
Quality / Stability / Reliability
-
False
-
-
False
-
-
-
Installer Train 36 - 3, Installer Train 37 - 4
-
Critical
-
None
Component Compliance Failure
Component: multiclusterhub-operator-acm-215
Application: acm-215
Scan Time: 2026-02-07T08:30:30Z
Image Build Time: 2026-02-05T20:54:20
Compliance Status
| Check | Status |
|---|---|
| Image Promotion | Successful(2026-02-05T20:54:20) |
| Hermetic Builds | Enabled |
| Enterprise Contract | Push Failure |
| Multiarch Support | Enabled |
| Push Pipeline | Failed |
Required Actions
- Fix pipeline push failures - component build is failing
- Fix push pipeline failures - check the build pipeline run logs for errors
Pipeline Run Links
- [Build Pipeline Run|https://konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/ns/crt-redhat-acm-tenant/pipelinerun/multiclusterhub-operator-acm-215-on-push-97h4r]
-------------------------------------------------------------------------------------------------------
QE Hand Off Template (fill out when moving to Review) 2/10/26:
Summary of the Work:
What was implemented or fixed? Include a brief description of the problem (if applicable) and how it was addressed.
e.g., "Updated the UI to show validation errors for the form. The previous implementation did not surface backend validation issues."
Key Areas to Verify:
- What functionality should QE focus on? List what was tested or what is most important to validate.
- Ensure the new validation messages appear for required fields
- Confirm the workflow still completes as expected after validation fixes
- Any edge cases or high-risk areas touched by the change
Fix or Feature Availability:
When will this be available in a build?
Code merged on: YYYY-MM-DD
Expected downstream build tag (if known): example-build-tag
(Optional) Related PR(s): Link