Skip to content
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
omarkalloush opened this issue Oct 13, 2022 · 4 comments · Fixed by #9909
Closed
2 of 3 tasks
Labels

Comments

@omarkalloush
Copy link

Pre-requisites

  • I have double-checked my configuration
  • I can confirm the issues exists when I tested with :latest
  • I'd like to contribute the fix myself (see contributing guide)

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.

# Run this twice and notice the 2nd workflow behavior
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: synchronization-wf-level-
spec:
  entrypoint: whalesay
  synchronization:
    mutex:
      name:  test
  templates:
    - name: whalesay
      container:
        image: docker/whalesay:latest
        command: [cowsay]
        args: ["hello world"]

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

@sarabala1979 sarabala1979 added area/ui P3 Low priority type/regression Regression from previous behavior (a specific type of bug) labels Oct 17, 2022
@sarabala1979
Copy link
Member

@omarkalloush can you provide the version which was working this?

@sarabala1979 sarabala1979 removed the type/regression Regression from previous behavior (a specific type of bug) label Oct 17, 2022
@omarkalloush
Copy link
Author

I have another environment with v3.3.9 it's working there

@omarkalloush
Copy link
Author

@sarabala1979 Any updates?

@isubasinghe
Copy link
Member

@omarkalloush thanks for creating this issue, this due to the filtering not being done correctly. I am creating a PR for this now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants