You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/iot-operations/troubleshoot/known-issues.md
-43Lines changed: 0 additions & 43 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -227,49 +227,6 @@ When you connect multiple IoT Operations instances to the same Event Grid MQTT n
227
227
228
228
To work around this issue, add randomness to the data flow names in your deployment templates.
229
229
230
-
### Data flow deployment doesn't complete
231
-
232
-
---
233
-
234
-
Issue ID: 9411
235
-
236
-
---
237
-
238
-
Log signature:
239
-
240
-
`"Dataflow pod had error: Bad pod condition: Pod 'aio-dataflow-operator-0' container 'aio-dataflow-operator' stuck in a bad state due to 'CrashLoopBackOff'"`
241
-
242
-
`"Failed to create webhook cert resources: Failed to update ApiError: Internal error occurred: failed calling webhook "webhook.cert-manager.io" [...]"`
243
-
244
-
---
245
-
246
-
When you create a new data flow, it might not finish deployment. The cause is that the `cert-manager` wasn't ready or running.
247
-
248
-
To work around this issue, use the following steps to manually delete the data flow operator pod to clear the crash status:
249
-
250
-
1. Run `kubectl get pods -n azure-iot-operations`.
251
-
In the output, Verify _aio-dataflow-operator-0_ is only data flow operator pod running.
252
-
253
-
1. Run `kubectl logs --namespace azure-iot-operations aio-dataflow-operator-0` to check the logs for the data flow operator pod.
254
-
255
-
In the output, check for the final log entry:
256
-
257
-
`Dataflow pod had error: Bad pod condition: Pod 'aio-dataflow-operator-0' container 'aio-dataflow-operator' stuck in a bad state due to 'CrashLoopBackOff'`
258
-
259
-
1. Run the _kubectl logs_ command again with the `--previous` option.
`Failed to create webhook cert resources: Failed to update ApiError: Internal error occurred: failed calling webhook "webhook.cert-manager.io" [...]`.
266
-
Issue ID:2382
267
-
If you see both log entries from the two _kubectl log_ commands, the cert-manager wasn't ready or running.
268
-
269
-
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.
270
-
271
-
1. Wait for the operator pod to restart and deploy the data flow.
0 commit comments