Merge pull request #125059 from chgennar/patch-1

Add Sporadic System Extension Failure to Known Issues

Author: v-dirichards

articles/iot-operations/troubleshoot/known-issues.md

@@ -23,6 +23,8 @@ This article lists the known issues for Azure IoT Operations.
 
 - During and after deploying Azure IoT Operations, you might see warnings about `Unable to retrieve some image pull secrets (regcred)` in the logs and Kubernetes events. These warnings are expected and don't affect the deployment and use of Azure IoT Operations.
 
+- If your deployment fails with the message `Error occurred while creating custom resources needed by system extensions`, you have encountered a known sporadic failure that will be fixed in a future release. As a work around, please delete Azure IoT Operations from your cluster using the [az iot ops delete](/cli/azure/iot/ops#az-iot-ops-delete) command and pass the `--include-deps` flag. Once Azure IoT Operations and its dependencies have been deleted from your cluster, the deployment can be retried.
+
 ## MQTT broker
 
 - MQTT broker resources created in your cluster using Kubernetes aren't visible Azure portal. This is expected because [managing Azure IoT Operations components using Kubernetes is in preview](../deploy-iot-ops/howto-manage-update-uninstall.md#preview-manage-components-using-kubernetes-deployment-manifests), and synchronizing resources from the edge to the cloud isn't currently supported.