Skip to content

Commit e54753d

Browse files
committed
Resolve 9411
1 parent 54e274e commit e54753d

File tree

1 file changed

+0
-43
lines changed

1 file changed

+0
-43
lines changed

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

Lines changed: 0 additions & 43 deletions
Original file line numberDiff line numberDiff line change
@@ -227,49 +227,6 @@ When you connect multiple IoT Operations instances to the same Event Grid MQTT n
227227

228228
To work around this issue, add randomness to the data flow names in your deployment templates.
229229

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.
260-
261-
`kubectl logs --namespace azure-iot-operations --previous aio-dataflow-operator-0`
262-
263-
In the output, check for the final log entry:
264-
265-
`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.
272-
273230
### Data flows error metrics
274231

275232
---

0 commit comments

Comments
 (0)