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

fix: use correct node name as args to PodName. Fixes #9906 #9995

Merged
merged 1 commit into from Nov 10, 2022

Conversation

isubasinghe
Copy link
Member

@isubasinghe isubasinghe commented Nov 8, 2022

Signed-off-by: Isitha Subasinghe isitha@pipekit.io

Fixes #9906

Please do not open a pull request until you have checked ALL of these:

  • Create the PR as draft .
  • Run make pre-commit -B to fix codegen and lint problems.
  • Sign-off your commits (otherwise the DCO check will fail).
  • Use a conventional commit message (otherwise the commit message check will fail).
  • "Fixes #" is in both the PR title (for release notes) and this description (to automatically link and close the issue).
  • Add unit or e2e tests. Say how you tested your changes. If you changed the UI, attach screenshots.
  • Github checks are green.
  • Once required tests have passed, mark your PR "Ready for review".

If changes were requested, and you've made them, dismiss the review to get it reviewed again.

@isubasinghe isubasinghe changed the title fix: use correct node name as args to PodName fix: use correct node name as args to PodName. Fixes #9906 Nov 8, 2022
@isubasinghe
Copy link
Member Author

The issue was with the PodName function, the name doesn't suggest this but it generates names for you using a hash of the fields.
PodName was called with the name+formatting applied to it, resulting in a different Hash.

This is the simplest fix, but I personally think it would be nicer if two functions existed. A GeneratePodName and GetPodName. This way the generation is more obvious.

@isubasinghe
Copy link
Member Author

image
Here is the working argo get command

@isubasinghe isubasinghe marked this pull request as ready for review November 8, 2022 10:34
Signed-off-by: Isitha Subasinghe <isitha@pipekit.io>
@terrytangyuan terrytangyuan merged commit 67bcdb5 into argoproj:master Nov 10, 2022
@isubasinghe isubasinghe deleted the fix-incorrect-pod-name branch November 10, 2022 07:43
@mweibel
Copy link
Contributor

mweibel commented Nov 11, 2022

is there a possibility to release this as a bugfix soon?

mweibel pushed a commit to helio/argo-workflows that referenced this pull request Nov 24, 2022
@caelan-io
Copy link
Member

@mweibel yes, we're looking at a new 3.4.4 patch release in the near future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/cli The `argo` CLI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Wrong Pod name in argo get command result from CLI
6 participants