-
Notifications
You must be signed in to change notification settings - Fork 906
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
Dashboard UI with namespace picker doesn't show individual rollout in other namespace #1334
Comments
I am having the same issue.
I am able to browse namespaces where there are rollouts, but when clicking into it, it returns an empty page. By the way, argo rollouts is an awesome product!!! |
@perenesenko could you look into this? |
Yes. I will look on it |
PR #1344 |
Hey @perenesenko, thanks for the fix! Do you know when this fix is planned for an official release? It seems it is not part of the 1.0.4 and 1.0.5 releases, but it is present on the master branch (unless I missed something 😄 ) Thanks! |
I tried running I do not see any warnings in the dashboard pod logs though, so maybe this is a different issue? |
Hmm I've been playing around with it some more and I think there's something about my Rollout that is causing it. Will update with more info/open a new issue if I can narrow it down. |
It's related to an ingress SSO solution that's in front of the dashboard, so ignore me. For anyone also trying to use the dashboard with buzzfeed SSO, the |
Summary
After #1291, it's possible to install the dashboard in one namespace and view Rollouts in another namespace. The main page which watches multiple Rollouts works fine and displays Rollouts in other namespaces. However, accessing the individual page for a Rollout in a different namespace shows an empty page.
The logs mention that the Rollout resource wasn't found. If I
kubectl argo rollouts dashboard
in the appropriate namespace, the "individual rollout page" works as expected.From the UI, the namespace looks to be correct in the
![image](https://user-images.githubusercontent.com/1437272/125096257-7ff66c80-e0c4-11eb-8399-56d02c14c906.png)
/watch
requestbut I notice in #1291 that
WatchRolloutInfos
was updated to get the context from thews
:argo-rollouts/server/server.go
Line 295 in ba21c6c
whereas
WatchRolloutInfo
is not accordingly updated, and still usescontext.Background()
argo-rollouts/server/server.go
Lines 213 to 214 in ba21c6c
Diagnostics
I'm running dashboard docker image
quay.io/argoproj/kubectl-argo-rollouts@sha256:c9d6c70161fa86aac4f9c0747049809c92e5b1d1356c0e62f3299d407f76c4ad
, which was the SHA of "latest" from last week.Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
The text was updated successfully, but these errors were encountered: