Description of problem:

When using a specific backup name (not "latest"), the credentials restore only creates the -active restore but skips the regular credentials restore.

Expected Behavior:

When restoring managed clusters with credentials, you should get TWO credential restores:

1. Regular credentials restore: restore-acm-creds-20251029181055-acm-credentials-schedule-20251029181055

1. Active credentials restore: restore-acm-creds-20251029181055-acm-credentials-schedule-20251029181055-active

Actual Behavior:

Only the -active restore is created when using a specific backup name.

Run a restore operation and use the backup name instead of the latest backup. For example use 
apiVersion: cluster.open-cluster-management.io/v1beta1
kind: Restore
metadata:
name: restore-acm-creds-20251029181055
namespace: open-cluster-management-backup
spec:
cleanupBeforeRestore: CleanupRestored
veleroManagedClustersBackupName: acm-managed-clusters-schedule-20251029181055
veleroCredentialsBackupName: acm-credentials-schedule-20251029181055
veleroResourcesBackupName: acm-resources-schedule-20251029181055
 
The restore status shows that the credentials backup was not restored

  phase: Finished

  veleroCredentialsRestoreName: restore-acm-creds-20251029181055-acm-credentials-schedule-20251029181055-active<< HERE I should get both -active and regular backup

  veleroGenericResourcesRestoreName: restore-acm-creds-20251029181055-acm-resources-generic-schedule-20251029181055

  veleroManagedClustersRestoreName: restore-acm-creds-20251029181055-acm-managed-clusters-schedule-20251029181055

  veleroResourcesRestoreName: restore-acm-creds-20251029181055-acm-resources-schedule-20251029181055

Version-Release number of selected component (if applicable):

How reproducible:

Always

Steps to Reproduce:

1. Restore with the attached sample
2. You should see a velero restore for the acm-credentials-schedule-20251029181055. You get only a velero for acm-credentials-schedule-20251029181055-active

Actual results: 

1. You should see a velero restore for the acm-credentials-schedule-20251029181055.

Expected results:

You get only a velero for acm-credentials-schedule-20251029181055-active

Additional info: 

I tested with ACM 2.15 but this is an issue with older releases as well

Related to this discussion

https://redhat-internal.slack.com/archives/C0282HW2YHZ/p1761763319860329?thread_ts=1761729892.038489&cid=C0282HW2YHZ