Bug 2180565

Summary:	Migration fails when there are multiple VSLs of different provider types configured in a cluster and no default VSL is set
Product:	Migration Toolkit for Containers	Reporter:	Pranav Gaikwad <pgaikwad>
Component:	Controller	Assignee:	John Matthews <jmatthew>
Status:	NEW ---	QA Contact:	ssingla
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	1.7.8	CC:	rjohnson
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pranav Gaikwad 2023-03-21 19:10:56 UTC

Description of problem:

When there are multiple VSLs in a cluster with different provider types, and none of them is set as default, Velero results in a validation error, making migrations fail. 

```
status:
  expiration: '2023-04-10T05:45:09Z'
  formatVersion: 1.1.0
  phase: FailedValidation
  validationErrors:
    - >-
      provider aws has more than one possible volume snapshot location, and none
      were specified explicitly or as a default
  version: 1
```

```
status:
  conditions:
    - category: Advisory
      durable: true
      lastTransitionTime: '2023-03-21T15:45:58Z'
      message: 'The migration has failed.  See: Errors.'
      reason: InitialBackupCreated
      status: 'True'
      type: Failed
  errors:
    - >-
      provider aws has more than one possible volume snapshot location, and none
      were specified explicitly or as a default
    - >-
      Backup openshift-migration/aiocptools-portal-cutover-2-initial-rll9b:
      validation failed.
```

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

How reproducible:
Always, apparently.

Steps to Reproduce:
This is purely from what I understood communicating with the customer.

1. Create 2 migstorages of GCP provider, create another 2 with AWS provider.
2. Run a migration selecting any one of the MigStorages. 

Actual results:
Migration fails with above error.

Expected results:
Migration should succeed.