When a cluster is provisioned via ZTP and no policies are immediately applied, TALM creates an automatic ClusterGroupUpgrade (CGU). The Cloud Events generated for this CGU (e.g., reason: CguSuccess) unexpectedly omit the cgu.openshift.io/cluster-name annotation.

This prevents Event-Driven Ansible (EDA) and other automation from reliably identifying the specific cluster that completed provisioning, as critical when conditions based on cluster-name fail. This breaks automated post-provisioning workflows, requiring manual intervention.

4.19 TALM events is devpreview    

Always

1.Provision a new OpenShift cluster using RHACM ZTP.
2. Ensure no explicit policies are applied to this cluster initially.
3. Monitor TALM Cloud Events from the MCGH agent.
4. Observe the CguSuccess event for the automatically created CGU: it will be missing eventAnnotations['cgu.openshift.io/cluster-name'].  

The TALM event for automatically created CGUs does not contain the cgu.openshift.io/cluster-name annotation, causing automation failures in EDA (e.g., item.eventAnnotations['cgu.openshift.io/cluster-name'] is defined evaluates to false).

The TALM event for the automatically created CGU should include the cgu.openshift.io/cluster-name annotation, populated with the cluster's name.

Impact: Breaks automated ZTP post-provisioning, leading to manual processes and incomplete event context for operations.

Workaround: None directly, forcing less precise automation or manual identification.