Skip to main content

Troubleshooting

Overview​

This guide helps you resolve common issues you might encounter while using Upwind with Azure. Below are various sections addressing specific problems, with step-by-step instructions to guide you through resolving them.

Common Issues​

Insufficient Spot VM Quota​

If you encounter issues with Spot VM deployment:

  1. Check your current quota: 
    az vm list-usage --location <region> --query "[?name.value=='lowPriorityCores']" --output table
  2. Request quota increase through Azure Portal if needed:
    • Go to Azure Portal → Subscriptions → Select your subscription
    • Click Settings and Usage + quotas
    • Find Spot vCPUs and request an increase
  3. Consider using a different region if quota increase is not immediately possible

Authentication Issues​

If you encounter authentication problems:

  1. Verify Azure CLI authentication: 
    az login
    az account list
  2. Ensure you have Owner privileges in the Azure tenant
  3. Check if the service principal has all required permissions

Client Secret Management​

When a client secret expires or needs to be updated:

In Azure Console​

  1. Navigate to App Registration:

    • Access the Azure application linked with Upwind
    • Go to "Certificates & Secrets" in the application settings

  2. Generate New Client Secret:

    • Click on "New client secret"
    • Set the expiration to at least 12 months
    • Note down the new client secret

    Alternatively, use Azure CLI:

    az ad app credential reset --id [Application (client) ID]

    The "password" field in the output is your new client secret.

In Upwind Management Console​

  1. Access Upwind Console:

  2. Update Client Secret:

    • Click the edit button next to the relevant subscription
    • Choose "Update Azure client secret"
    • Enter the new client secret and click "Test account connectivity"

Migration from azure-cloud-credentials​

warning

Migration from azure-cloud-credentials is currently not supported. We are working on adjustments in credential handling to support this scenario.

For customers already using azure-cloud-credentials, we recommend:

  1. Wait for migration support to be available
  2. Keep existing configuration until migration path is ready
  3. Contact support for specific migration timeline and guidance

Support​

If you encounter any issues not covered in this guide:

  1. Check the Azure Activity Log for any error messages
  2. Review RBAC assignments and permissions
  3. Contact Upwind support with:
    • Detailed error messages
    • Azure subscription ID
    • Resource group name
    • Relevant log entries