-
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
Wrong podName in workflow.status #10124
Comments
sarabala1979
added
the
P2
Important. All bugs with >=3 thumbs up that aren’t P0 or P1, plus: Any other bugs deemed important
label
Nov 28, 2022
This was referenced Dec 21, 2022
alexec
pushed a commit
that referenced
this issue
Jan 5, 2023
reddymh
pushed a commit
to reddymh/argo-workflows
that referenced
this issue
Jan 31, 2023
… (argoproj#10268) Signed-off-by: Isitha Subasinghe <isitha@pipekit.io> Signed-off-by: Rajshekar Reddy <reddymh@gmail.com>
@alexec - Is it possible that the UI is still having this issue sometimes ? |
3 tasks
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?
workflow.status contains podName, but wrong. It doesn't include the template name in the middle of the name.
podName from workflow.status is: dev-test-jpx47-486552824
Real pod name in kubernetes is: dev-test-jpx47-test-template-486552824
Version
latest
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
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: