-
-
Notifications
You must be signed in to change notification settings - Fork 307
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
shuffle workflow in executing state and pods are in error state #1384
Comments
Hey, could you find logs for cd7b9999-bffe-4bc6-b31a-123456 on the This can be prevented all the time if cache between Workers and the Backend are in place, which it isn't by default. Docker reference for it: |
Line 91 in 06ac921
|
Hi @frikky |
Hey! We need a lot more details to look into this. Please find the logs for Orborus and the deployed Workers under it. The easiest way to do this is to start a random workflow that has delays in it, then checking the worker logs. K8s is still a beta feature and not fully functional with e.g. service accounts & namespace control as it should have, and e could really need some more help :) |
``Hi @frikky
And here is the worker pod log
|
Hi @frikky I'm facing an issue with the shuffle workflow. The shuffle workflow has webhook which is integrated with wazuh and based on the condition it will create case in thhive. Eventhough the case is creating in thhive but the workflow is still in executing state
And the shuffle worker pod is in error state. This is the logs i'm getting
Here it is showing the
Upload_file_to_S3', Action: 'AWS S3', Status: SUCCESS
but the action is already skipped in the workflow based on the condition.So if the cases is successfully created means the workflow should be in success state and the pods should be in completed state right?
Need your help on this @frikky
The text was updated successfully, but these errors were encountered: