-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Workflows in the Pending state that are waiting for the mutex are not showing in the UI #9812
Closed
2 of 3 tasks
Comments
sarabala1979
added
area/ui
P3
Low priority
type/regression
Regression from previous behavior (a specific type of bug)
labels
Oct 17, 2022
@omarkalloush can you provide the version which was working this? |
sarabala1979
removed
the
type/regression
Regression from previous behavior (a specific type of bug)
label
Oct 17, 2022
I have another environment with v3.3.9 it's working there |
@sarabala1979 Any updates? |
@omarkalloush thanks for creating this issue, this due to the filtering not being done correctly. I am creating a PR for this now. |
8 tasks
terrytangyuan
pushed a commit
that referenced
this issue
Nov 1, 2022
Radolumbo
pushed a commit
to Radolumbo/argo-workflows
that referenced
this issue
Nov 2, 2022
…oproj#9909) Signed-off-by: Nick Palumbo <[email protected]>
juchaosong
pushed a commit
to juchaosong/argo-workflows
that referenced
this issue
Nov 3, 2022
…oproj#9909) Signed-off-by: juchao <[email protected]>
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Pre-requisites
:latest
What happened/what you expected to happen?
What happened?
I deployed 2 workflows that has the same mutex the 2nd one wasn't visible in the UI till the 1st one finished
What is expected to happen?
The 2nd one used to be shown in the UI with the yellow mark saying it's pending and waiting for the mutex
Version
v3.4.1
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
Logs from the workflow controller
kubectl logs -n argo deploy/workflow-controller | grep ${workflow}
Logs from in your workflow's wait container
kubectl logs -n argo -c wait -l workflows.argoproj.io/workflow=${workflow},workflow.argoproj.io/phase!=Succeeded
The text was updated successfully, but these errors were encountered: