Skip to content

Commit c26d528

Browse files
committed
Add Akri known issue
1 parent 3cad112 commit c26d528

File tree

1 file changed

+22
-2
lines changed

1 file changed

+22
-2
lines changed

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

Lines changed: 22 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Known issues for the MQTT broker, Layered Network Management (previ
44
author: dominicbetts
55
ms.author: dobett
66
ms.topic: troubleshooting-known-issue
7-
ms.date: 05/07/2025
7+
ms.date: 05/22/2025
88
---
99

1010
# Known issues: Azure IoT Operations
@@ -204,6 +204,26 @@ To work around this issue, complete the following steps to manually delete the C
204204

205205
1. Uninstall Helm release without running the hook: `helm uninstall aio-<id>-connectors -n azure-iot-operations --no-hooks`
206206

207+
## Asset discovery with Akri services issues
208+
209+
This section lists current known issues for asset discovery with Akri services.
210+
211+
### Asset discovery doesn't work for one hour after upgrade
212+
213+
---
214+
215+
Issue ID: 0407
216+
217+
---
218+
219+
Log signature: N/A
220+
221+
---
222+
223+
When you upgrade the Akri services, you might experience some loss of messages and assets for an hour after the upgrade.
224+
225+
To workaround this issue, wait for an hour after the upgrade and run the asset detection scenario again.
226+
207227
## Data flows issues
208228

209229
This section lists current known issues for data flows.
@@ -290,7 +310,7 @@ To work around this issue, use the following steps to manually delete the data f
290310
In the output, check for the final log entry:
291311

292312
`Failed to create webhook cert resources: Failed to update ApiError: Internal error occurred: failed calling webhook "webhook.cert-manager.io" [...]`.
293-
313+
Issue ID:2382
294314
If you see both log entries from the two _kubectl log_ commands, the cert-manager wasn't ready or running.
295315

296316
1. Run `kubectl delete pod aio-dataflow-operator-0 -n azure-iot-operations` to delete the data flow operator pod. Deleting the pod clears the crash status and restarts the pod.

0 commit comments

Comments
 (0)