-
Bug
-
Resolution: Done-Errata
-
Normal
-
None
-
None
-
False
-
None
-
False
-
-
It was reported that the operator failed on timeout when calling forklift-api.openshift-mtv.svc:443/provider-validate?timeout=10s
ESC[0;31mfatal: [localhost]: FAILED! => {"changed": false, "error": 500, "msg": "Failed to create object: b'{\"kind\":\"Status\",\"apiVersion\":\"v1\",\"metadata\":{},\"status\":\"Failure\",\"message\":\"Internal error occurred: failed calling webhook \\\\\"providers.forklift.konveyor\\\\\": failed to call webhook: Post \\\\\"https://forklift-api.openshift-mtv.svc:443/provider-validate?timeout=10s\\\\\": context deadline exceeded\",\"reason\":\"InternalError\",\"details\":{\"causes\":[{\"message\":\"failed calling webhook \\\\\"providers.forklift.konveyor\\\\\": failed to call webhook: Post \\\\\"https://forklift-api.openshift-mtv.svc:443/provider-validate?timeout=10s\\\\\": context deadline exceeded\"}]},\"code\":500}\\n'", "reason": "Internal Server Error", "status": 500}ESC[0m
We see in forklift-api that it indeed took more than 10 seconds to execute the wehbook. It was triggered at 12:51:10.213:
| {"level":"info","ts":"2023-09-27 12:51:10.213","logger":"admitter","msg":"Provider admitter was called"} |
and still executed at 12:51:26.274:
| {"level":"info","ts":"2023-09-27 12:51:26.274","logger":"admitter","msg":"Provider of this type does not require VDDK, passing","type":"openshift"} |
We should make the timeout configurable but as a temporary solution we can increase it to 30 seconds as we do for the mutating webhooks
- is cloned by
-
-
- Closed
-
- links to
-
RHBA-2024:126311
MTV 2.6.0 Images
