+++ This bug was initially created as a clone of Bug #1784447 +++ Description of problem: When an Azure storage object it defined in a Azure to Azure migration, the secret is not correctly identified and velero fails with an error. Version-Release number of selected component (if applicable): $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.2.0-0.nightly-2019-12-15-230238 True False 3h4m Cluster version is 4.2.0-0.nightly-2019-12-15-230238 Operator: 1.0.1 osbs images image: image-registry.openshift-image-registry.svc:5000/rhcam-1-0/openshift-migration-rhel7-operator@sha256:f41484cbe7dbc4e4522fbcd63adc0dc926d463e3516c82ec4360a91441f84fd4 Controller: 1.0.1 osbs images image: image-registry.openshift-image-registry.svc:5000/rhcam-1-0/openshift-migration-controller-rhel8@sha256:e2c3cbb61157605d8246496f77c76b9b2950eb951bd0a63d4f8e3ae6f1884c2c Velero: image-registry.openshift-image-registry.svc:5000/rhcam-1-0/openshift-migration-plugin-rhel8@sha256:9107a197ab0a1a5a13e47c0c9cd4582de81745f916b6a28aa78cb09428e00afa image-registry.openshift-image-registry.svc:5000/rhcam-1-0/openshift-migration-velero-rhel8@sha256:c59e1b3f35376fbf71352dba72710a9a4395c172168adfe3d57eb8dbf23194bb How reproducible: Always Steps to Reproduce: 1. Create 2 Azure clusters 2. Install App migration tool in order to migrate from source to target. 3. Use an Azure storage object to perform the migration 4. Migrate any application Actual results: Velero gives this error and migration cannot be executed. time="2019-12-16T17:19:03Z" level=error msg="Error getting backup store for this location" backupLocation=azure-qlk7n controller=backup-sync error="rpc error: code = Unknown desc = unable to get all required environment variables: the following keys do not have values: AZURE_TENANT_ID, AZURE_CLIENT_ID, AZURE_CLIENT_SECRET, AZURE_SUBSCRIPTION_ID" error.file="/go/src/github.com/heptio/velero/pkg/cloudprovider/azure/object_store.go:146" error.function=github.com/heptio/velero/pkg/cloudprovider/azure.getStorageAccountKey logSource="pkg/controller/backup_sync_controller.go:168" Expected results: The storage object should be handled properly and the migrations should finish with no failures Additional info: This problem happens because controller and operator are out of sync here: https://github.com/fusor/mig-operator/pull/166 and https://github.com/fusor/mig-controller/pull/373 are related Both need to be merged to 1.0.1 version.
Verified in CAM 1.1 stage azure 4.3 -> azure 4.3 Controller: imageID: image-registry.openshift-image-registry.svc:5000/rhcam-1-1/openshift-migration-controller-rhel8@sha256:44e0b889db53f97abea549d9dcd4ad9b2491a4ff31e6d1afc251596d60c104b5 Velero: imageID: image-registry.openshift-image-registry.svc:5000/rhcam-1-1/openshift-migration-velero-rhel8@sha256:29ab439545c0dc765af23b287721a766879647a750443e39658e1894d38555fc imageID: image-registry.openshift-image-registry.svc:5000/rhcam-1-1/openshift-migration-plugin-rhel8@sha256:9c6eceba0c422b9f375c3ab785ff392093493ce33def7c761d7cedc51cde775d imageID: image-registry.openshift-image-registry.svc:5000/rhcam-1-1/openshift-migration-velero-plugin-for-aws-rhel8@sha256:5235eeeee330165eef77ac8d823eed384c9108884f6be49c9ab47944051af91e imageID: image-registry.openshift-image-registry.svc:5000/rhcam-1-1/openshift-migration-velero-plugin-for-gcp-rhel8@sha256:789b12ff351d3edde735b9f5eebe494a8ac5a94604b419dfd84e87d073b04e9e imageID: image-registry.openshift-image-registry.svc:5000/rhcam-1-1/openshift-migration-velero-plugin-for-microsoft-azure-rhel8@sha256:b98f1c61ba347aaa0c8dac5c34b6be4b8cce20c8ff462f476a3347d767ad0a93 Volumes were migrated without problems using an Azure storage account (managed-premium storage class).
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2020:0440