Skip to content

Commit 6536a2e

Browse files
authored
Fix typo in known issues documentation
1 parent 28354ca commit 6536a2e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ This article lists the known issues for Azure IoT Operations.
2323

2424
- 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.
2525

26-
- 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](https://learn.microsoft.com/en-us/cli/azure/iot/ops?view=azure-cli-latest#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 of can be retried.
26+
- 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](https://learn.microsoft.com/en-us/cli/azure/iot/ops?view=azure-cli-latest#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.
2727

2828
## MQTT broker
2929

0 commit comments

Comments
 (0)