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

Namespace filter not being cleared #4348

Closed
andyleap opened this issue Oct 22, 2020 · 4 comments
Closed

Namespace filter not being cleared #4348

andyleap opened this issue Oct 22, 2020 · 4 comments
Labels

Comments

@andyleap
Copy link

Summary

What happened/what you expected to happen?

What happened:

  1. Open argo ui
  2. Enter namespace and hit enter
  3. Clear namespace with x
  4. Reload UI (or any other kind of navigation away from and back to argo root
  5. Namespace from step 2 is back

Expected:
Step 5 would show workflows from all namespaces.

Diagnostics

What Kubernetes provider are you using? GKE

What version of Argo Workflows are you running? 2.11.5


Message from the maintainers:

Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

@alexec
Copy link
Contributor

alexec commented Dec 14, 2020

Is this still a problem in v2.12 please?

@thundergolfer
Copy link

We're using v2.12.3 and I still observe this issue, but with the URL being populated with a workflow ID. I took a video of the behaviour, but can't upload as it contains private info. Step-wise, the behaviour is:

  1. Go to Argo UI. Url is <BASE_URL>/workflows/foo-bar-workflow-jlc54
  2. Navigate to "Archived Workflows" tab, and URL is populated as <BASE_URL>/archived-workflows/foo-bar-workflow-jlc54?minStartedAt=... so "no archived workflows" show up.
  3. Remove everything from that URL after archived-workflows/ and correctly see all the archived workflows.
  4. Navigate back to main workflows tab, and URL is back to <BASE_URL>/workflows/foo-bar-workflow-jlc54 so "No workflows" show up.

@alexec
Copy link
Contributor

alexec commented Jan 20, 2021

can you try with :latest?

@alexec
Copy link
Contributor

alexec commented Mar 17, 2021

Assumed fixed in v3

@alexec alexec closed this as completed Mar 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants