Description of problem: When we configure in the same CAM one replication repository for AWS and another one for Noobaa, the migrations fail. Version-Release number of selected component (if applicable): CAM 1.2 stage How reproducible: Always Steps to Reproduce: 1. Add an AWS replication repository to your CAM 2. Add a Noobaa replication repository to your CAM 3. Create a migration plan using the AWS replication repository (any applicaiton) 4. Create a migration plan using the noobaa replication repository (any application) 5. Migrate both plans. Actual results: There is a problem with the replication repositories credentials, and the migrations fail. This failure is reported time="2020-05-11T11:13:55Z" level=error msg="Error listing backups in backup store" backupLocation=noobaa-q8t7l controller=backup-sync error="rpc error: code = Unknown desc = AccessDenied: Access Denied\n\tstatus code: 403, request id: ka2e1s60-40jfg1-1cjr, host id: ka2e1s60-40jfg1-1cjr" error.file="/go/src/github.com/konveyor/openshift-migration-velero-plugin-for-aws/velero-plugin-for-aws/object_store.go:324" error.function="main.(*ObjectStore).ListCommonPrefixes" logSource="pkg/controller/backup_sync_controller.go:174" time="2020-05-11T11:14:25Z" level=error msg="Error listing backups in backup store" backupLocation=automatic-qnlfx controller=backup-sync error="rpc error: code = Unknown desc = InvalidAccessKeyId: The AWS Access Key Id you provided does not exist in our records.\n\tstatus code: 403, request id: F4097XXXXXECD9C, host id: eo5Las+ciRvsmlID2S9ye2iWWU6fXXXXXXX2IpubXv0PNa7n7gXQNrRXowhR3iPqbk5H2A=" error.file="/go/src/github.com/konveyor/openshift-migration-velero-plugin-for-aws/velero-plugin-for-aws/object_store.go:324" error.function="main.(*ObjectStore).ListCommonPrefixes" logSource="pkg/controller/backup_sync_controller.go:174" time="2020-05-11T11:14:55Z" level=error msg="Error listing backups Expected results: Both migrations should be executed without problems. Additional info:
Need to confirm whether or not this remains an issue
Closing as stale, please re-open if the BZ remains relevant with the current release.
This is a significant departure from 1.3.0 where this was actually filed. Can you please open a new bug, set the "Version" field to 1.5.3, and then close this bug? I don't think that this is related to the original issue raised here. @vkochuku
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days