Kopia backup failed in Azure if "AZURE_CLOUD_NAME" exists in credential file

[ywk253100]

Velero is installed on Azure with the credential file as follows:

AZURE_SUBSCRIPTION_ID=xxx
AZURE_TENANT_ID=xxx
AZURE_CLIENT_ID=xxx
AZURE_CLIENT_SECRET=xxx
AZURE_RESOURCE_GROUP=xxx
#AZURE_CLOUD_NAME=AzurePublicCloud

Do the first backup for the workload in namespace 1 with Kopia, the backup is successful, but the second backup for the workload in another namespace 2 will fail, the backup repository report the following error:

yinw@yinw-a02 tests % kubectl -n velero get backuprepository default-default-kopia-zjwrg -o yaml
apiVersion: velero.io/v1
kind: BackupRepository
metadata:
  creationTimestamp: "2022-10-27T08:54:09Z"
  generateName: default-default-kopia-
  generation: 4
  labels:
    velero.io/repository-type: kopia
    velero.io/storage-location: default
    velero.io/volume-namespace: default
  name: default-default-kopia-zjwrg
  namespace: velero
  resourceVersion: "111851"
  uid: 3a15cb09-2d9e-40bf-a786-d835b164432d
spec:
  backupStorageLocation: default
  maintenanceFrequency: 1h0m0s
  repositoryType: kopia
  resticIdentifier: azure:velero:/restic/default
  volumeNamespace: default
status:
  message: 'error to init backup repo: error to connect to storage: unable to list
    from the bucket: Get "https://yinwstorageaccount01.azurepubliccloud/velero?comp=list&include=metadata&prefix=kopia%2Fdefault%2Fkopia-azure-storage-initializing-1666860979301866646&restype=container":
    dial tcp: lookup yinwstorageaccount01.AzurePublicCloud on 10.0.0.10:53: no such
    host'
  phase: NotReady

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

• 👍 for "I would like to see this bug fixed as soon as possible"
• 👎 for "There are more important bugs to focus on right now"

[Lyndon-Li]

fixed by #5512