Normal Related to https://issues.redhat.com/browse/TECE-280
Many images are either stale, private or not working as expected (running as root, wrong command, etc). We need to make sure the correct images are available
| Operand Image Name | Quay Repository | Status |
|---|---|---|
| OPERAND_IMAGE_CLUSTER_API_PROVIDER_OPENSHIFT_ASSISTED_BOOTSTRAP | quay.io/stolostron/cluster-api-provider-openshift-assisted-bootstrap | repository is stale, image last built 4 months ago and only the 'latest' tag is present currently using this image to deploy MCE on k8s: quay.io/edge-infrastructure/cluster-api-bootstrap-provider-openshift-assisted:latest |
| OPERAND_IMAGE_CLUSTER_API_PROVIDER_OPENSHIFT_ASSISTED_CONTROL_PLANE | quay.io/stolostron/cluster-api-provider-openshift-assisted-control-plane | repository is stale, image last built 4 months ago and only the 'latest' tag is present currently using this image to deploy MCE on k8s: quay.io/edge-infrastructure/cluster-api-controlplane-provider-openshift-assisted:latest |
| OPERAND_IMAGE_CLUSTER_API_WEBHOOK_CONFIG_MCE_29 | ? | image is undefined in the upstream backplane-operator bundle and no repository appears to exist. Note: this is most likely not needed |
| OPERAND_IMAGE_OSE_BAREMETAL_CLUSTER_API_CONTROLLERS_RHEL9 | quay.io/stolostron/ose-baremetal-cluster-api-controllers-rhel9 | repository is stale, image last built 4 months ago and only the 'latest' tag is present |
| OPERAND_IMAGE_OSE_CLUSTER_API_RHEL9 | quay.io/stolostron/ose_cluster_api_rhel9 | repository is missing or non-public |
-------------------------------------------------------------------------------------------------------
QE Hand Off Template (fill out when moving to Review) 11/7/25:
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
