1) Identify potential solution for cleanup if some failure or interruption in Jenkins ci build for testing.

• Jenkins Post build or Pre-build cleanup script
• Can we look into ginkgo for any support for a pre run clean up function like (auto use fixtures in pytest)
• Brainstorm with team for any other potential solutions for the use case.

2)The periodic int failed by interruption in the last step almost; Then it tried several times to delete the clusters:
And the job is waiting to a status unreachable since the cluster is already in cleanup_ack_pending. The cleanup should be smart enough to identify the current status and follow up from that.
14:16:56 ServiceCluster with ID :d4pap6lfm5ac73ccrnng and ManagementCluster with ID : will be cleaned up 14:16:56 STEP: Sending deletion request @ 12/05/25 14:16:56.747 14:16:56 Waiting for Service Cluster [d4pap6lfm5ac73ccrnng] to be deprovisioning, current status: cleanup_ack_pending 14:16:56 14:17:57 Waiting for Service Cluster [d4pap6lfm5ac73ccrnng] to be deprovisioning, current status: cleanup_ack_pending 14:17:57 14:18:57 Waiting for Service Cluster [d4pap6lfm5ac73ccrnng] to be deprovisioning, current status: cleanup_ack_pending 14:18:57 14:19:57 Waiting for Service Cluster [d4pap6lfm5ac73ccrnng] to be deprovisioning, current status: cleanup_ack_pending 14:19:57 14:20:57 Waiting for Service Cluster [d4pap6lfm5ac73ccrnng] to be deprovisioning, current status: cleanup_ack_pending 14:20:57 14:21:57 Waiting for Service Cluster [d4pap6lfm5ac73ccrnng] to be deprovisioning, current status: cleanup_ack_pending 14:21:57 14:22:57 Waiting for Service Cluster [d4pap6lfm5ac73ccrnng] to be deprovisioning, current status: cleanup_ack_pending
 
HAD TO ACK MANUALLY TO GET IT FIXED.

3)we should remove this auto-trigger after a failure.
or add a lower limit for that
 
we should remove this auto-trigger after a failure
or add a lower limit for that
 

REFERENCE: https://redhat-internal.slack.com/archives/C035W96HKN3/p1764945192208899?thread_ts=1764943209.315889&cid=C035W96HKN3