Credential creation errors on Azure
The following errors may occur during credential creation.
Role already exists
Error: Role already exists in Azure with the name: CloudbreakCustom50
Solution: This error occurs because you specified that you want to create a new
role for Cloudbreak credential, but an existing role with the same
name already exists in Azure. To solve this, you should either rename the role during
credential creation or select the Reuse existing custom role
option.
Role does not exist
Error: Role does not exist in Azure with the name: CloudbreakCustom60
Solution: This error occurs because you specified that you want to reuse an
existing role for your Cloudbreak credential, but that particular
role does not exist in Azure. To solve this, you should either rename the new role
during the credential creation to match the existing role’s name or select the
Let Cloudbreak create a custom role option.
Role does not have enough privileges
Error: CloudbreakCustom 50 role does not have enough privileges to be used by Cloudbreak!
Solution: This error occurs because you specified that you want to reuse an
existing role for your Cloudbreak credential, but that particular
role does not have the necessary privileges for Cloudbreak cluster
management. To solve this, you should either select an existing role with enough
privileges or select the Let Cloudbreak create a custom role option.
The necessary action set for Cloudbreak to be able to manage the
clusters includes: "Microsoft.Compute/*", "Microsoft.Network/*",
"Microsoft.Storage/*", "Microsoft.Resources/*"
Client does not have authorization
Error: Failed to verify credential: Status code 403, {“error”:{“code”:”AuthorizationFailed”, “message”:”The client ‘X’ with object id ‘z’ does not have authorization to perform action ‘Microsoft.Storage/storageAccounts/read’ over scope ‘subscriptions/…’”}
Solution: This means that your Azure account does not have sufficient permissions
to create a Coudbreak credential. If you get this error during interactive credential
creation, ensure that your Azure account has
Microsoft.Authorization/*/Write permission; Otherwise contact your
Azure administrator to either give your account that permission or create the necessary
resources for the app-based credential creation method.
Cloud not validate publickey certificate
Error: Could not validate publickey certificate [certificate: ‘fdfdsf’], detailed message: Corrupt or unknown public key file format
Solution: The syntax of your SSH public key is incorrect. You must correct the syntax of your SSH key. For information about the correct syntax, refer to this page.