-
Notifications
You must be signed in to change notification settings - Fork 880
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
AnalysisRun gets stuck in Running state for dryrun + successful job metric #2151
Comments
@agrawroh can you check the above usecase? |
Sorry for the delayed response. This definitely looks like a bug. I'll try to repro on my end and would open a fix PR. @chrisplim Could you please share the output of the |
@agrawroh AnalysisRun output
|
Thanks, @chrisplim. Could you please also do "kubectl describe ar " and then paste that screenshot? To see the latest analysis run, you can do "kubectl get ar" |
@agrawroh
|
Hi @agrawroh, I was trying to test the fix on release 1.3.0, but it seems I get the same behavior when I run through the reproducing steps in the PR description. kubectl argo rollouts version
kubectl describe ar
kubectl logs -n argo-rollouts deployment/argo-rollouts | grep analysisrun= | grep "2022-10-06"
|
Following up. It seems that the fix didn't actually get picked up in release 1.3.0 (I misread one of the commits) |
@chrisplim can you try with 1.3.1 release and confirm if still an issue? |
@harikrongali Hello, it seems like the commit made it into the |
Checklist:
Describe the bug
AnalysisRun gets stuck in
Running
state if the metric is listed as a dryrun and is a Job that completes Successfully with exit code 0.To Reproduce
Running
state toSuccessful
Expected behavior
The AnalysisRun should transition to the
Successful
state after a Job completes successfully with exit code 0, even though the metric was listed as a dryRun.Note: We can verify that the dryrun with a failed job works as expected, which is to transition the AnalysisRun to be
Successful
, despite the Job failing.steps:
spec.strategy.blueGreen.prePromotionAnalysis.templates[0].templateName
to bedryrun-analysis-failure
kubectl apply -f dryrun-manifests.yaml
Screenshots
Screenshot showing the job completed successfully, but AnalysisRun gets stuck in Running state
(the output of
kubectl argo rollouts get rollout dryrun-rollout --watch
)Screenshot showing output of
kubectl get pods
08f-ee71755d698d.png">
Screenshot showing output of
kubectl describe pod 25d8853f-6d87-4358-83a7-44d8bf6238f6.test.1-vvqng
Version
Logs
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: