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

Status command output differs depending on the flag is set as --watch=true or --watch=false #1391

Closed
tsurankov opened this issue Aug 3, 2021 · 1 comment · Fixed by #1433
Assignees
Labels
bug Something isn't working good first issue Good for newcomers help wanted Extra attention is needed

Comments

@tsurankov
Copy link

Summary

The output of the status command is different if we run status with the --watch flag set to true or false. I am not sure if it was designed in that way, but for me, it is a bit confusing. Let's compare:

kubectl-argo-rollouts status example-spring-boot-prod-01 --namespace test-argo-prod --watch=true
Paused - BlueGreenPause
kubectl-argo-rollouts status example-spring-boot-prod-01 --namespace test-argo-prod --watch=false
Paused

kubectl-argo-rollouts status example-spring-boot-prod-01 --namespace test-argo-prod --watch=true
Progressing - active service cutover pending
kubectl-argo-rollouts status example-spring-boot-prod-01 --namespace test-argo-prod --watch=false
Progressing

Diagnostics

What version of Argo Rollouts are you running?
1.0.4


Message from the maintainers:

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

@tsurankov tsurankov added the bug Something isn't working label Aug 3, 2021
@jessesuen jessesuen added good first issue Good for newcomers help wanted Extra attention is needed labels Aug 4, 2021
@huikang huikang self-assigned this Sep 14, 2021
@huikang
Copy link
Member

huikang commented Sep 14, 2021

Hi, @tsurankov , the PR should resolve this bug; here is some sample output: #1433 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants