az iot ops create fails with an HelmInstallTimeout (Quickstart guide)

Question

I followed the steps of the "Quickstart: Run Azure IoT Operations Preview in GitHub Codespaces with K3s" Guide.

However, when I want to deploy Azure IoT Operations, with the command az iot ops create --cluster $CLUSTER_NAME --resource-group $RESOURCE_GROUP --name ${CLUSTER_NAME}-instance I run into an timeout after ~31/32 minutes:

(DeploymentFailed) At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.
Code: DeploymentFailed
Message: At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.
Target: /subscriptions/<SUBSCRIPTIONID>/resourceGroups/A_IoT_OP_Test_NorthEU/providers/Microsoft.Resources/deployments/aziotops.instance.6d66a9afe210450d99c0e9a03f96fa2a
Exception Details:      (ResourceDeploymentFailure) The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'.
        Code: ResourceDeploymentFailure
        Message: The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'.
        Target: /subscriptions/<SUBSCRIPTIONID>
        Exception Details:      (HelmInstallTimeout) The Helm install operation for the release azure-iot-operations-test-northe-8ac4-schemaregistry in the namespace azure-iot-operations has timed out after 10m0s. Please verify the cluster status, check for sufficient resources, and try again.
                Code: HelmInstallTimeout
                Message: The Helm install operation for the release azure-iot-operations-test-northe-8ac4-schemaregistry in the namespace azure-iot-operations has timed out after 10m0s. Please verify the cluster status, check for sufficient resources, and try again.
                Target: SchemaRegistry
                Exception Details:      (Unknown) release azure-iot-operations-test-northe-8ac4-schemaregistry failed, and has been uninstalled due to atomic being set: context deadline exceeded
                        Code: Unknown
                        Message: release azure-iot-operations-test-northe-8ac4-schemaregistry failed, and has been uninstalled due to atomic being set: context deadline exceeded

Does anyone else know a solution to fix this?

I'm running this without Codespaces but in a devcontainer that is running with rancher desktop 1.16.0 (moby) and Kubernetes v.1.30.4 (I manually set the CLUSTER_NAME environment variable (devcontainer.json)), and tried it on 2 azure locations, westeurope and northeurope. I could avoid the crash that occurs when running az connectedk8s connect --name $CLUSTER_NAME --location $LOCATION --resource-group $RESOURCE_GROUP by upgrading the connectedk8s extension (az extension update --name connectedk8s) and have the following extension list installed:

$ az extension list
[
  {
    "experimental": false,
    "extensionType": "whl",
    "name": "azure-iot-ops",
    "path": "/home/codespace/.azure/cliextensions/azure-iot-ops",
    "preview": true,
    "version": "0.7.0b1"
  },
  {
    "experimental": false,
    "extensionType": "whl",
    "name": "connectedk8s",
    "path": "/home/codespace/.azure/cliextensions/connectedk8s",
    "preview": false,
    "version": "1.9.3"
  },
  {
    "experimental": false,
    "extensionType": "whl",
    "name": "k8s-extension",
    "path": "/home/codespace/.azure/cliextensions/k8s-extension",
    "preview": false,
    "version": "1.6.1"
  }
]

Any suggestions?

Answer 1

unbacked-sc storage class is only created when a local-path provisioner is present. 

Can you retry after doing:  kubectl apply -f`` https://raw.githubusercontent.com/Azure/AKS-Edge/main/samples/storage/local-path-provisioner/local-path-storage.yaml

Answer 2

I figured that the PVC required a readwritemany volume. After providing this and creating a storage class called unbacked-sc, it worked for me