-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
open artifact : permission denied #4338
Comments
Is the HTTP status code 403? If so, you probably don’t have the correct Kubernetes RBAC permission set up. |
I experienced this from a quick start installation as well. After reapplying the RBAC roles and bindings, the issue went away. I suspect this might have something to do with the quick start manifests. |
Can you provide the exact files you find yourself applying? It might be that they are not listed correctly. |
Just this onequick-start-postgres.yaml |
Signed-off-by: Alex Collins <alex_collins@intuit.com>
…j#4350) Signed-off-by: Alex Collins <alex_collins@intuit.com> Signed-off-by: Alex Capras <alexcapras@gmail.com>
Summary
What happened:
I installed the quick-start-postgres.yaml, submitted the example using the argo UI. After the example succeeded,I want to see the logs in Archived Workflows, but it shows "Internal Server Error". Then I clicked on" logs from the artifacts", but it shows "open artifact788239015: permission denied". I clicked on "OUTPUT ARTIFACTS" and I can see the file"main-logs", but when I clicked on it, stil, "open artifact083636081: permission denied"
What version of Argo Workflows are you running?
v2.11.6
argo-server logs
workflow-controller logs
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered: