azure-pipelines-tasks: helm3 - setting system.debug causes "helm upgrade" pipeline to be marked as fail even though it succeeded
Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug/Feature
Enter Task Name: helm
Environment
- Server - Azure Pipelines or TFS on-premises? Azure DevOps / Pipelines
Issue Description
The debug output of helm3 is being treated as an error message. This causes the stage to be marked as failed
To reproduce, set the pipeline variable system.debug to true.
2019-09-19T17:42:18.7081006Z ##[debug]execResult: {"code":0,"stdout":"NAME: project-dev\nLAST DEPLOYED: 2019-09-19 17:42:15.684362147 +0000 UTC m=+0.537851092\nNAMESPACE: project-dev\nSTATUS: deployed\nRelease \"project-dev\" has been upgraded. Happy Helming!\nNAME: project-dev\nLAST DEPLOYED: 2019-09-19 17:42:15.684362147 +0000 UTC\nNAMESPACE: project-dev\nSTATUS: deployed\n","stderr":"history.go:52: [debug] getting history for release project-dev\nupgrade.go:79: [debug] preparing upgrade for project-dev\nupgrade.go:88: [debug] creating upgraded release for project-dev\nupgrade.go:94: [debug] performing update for project-dev\nclient.go:140: [debug] checking 4 resources for changes\nwait.go:50: [debug] beginning wait for 4 resources with timeout of 5m0s\nupgrade.go:101: [debug] updating status for upgraded release for project-dev\n"}
2019-09-19T17:42:18.7082076Z ##[debug]task result: Failed
2019-09-19T17:42:18.7138882Z ##[error]history.go:52: [debug] getting history for release project-dev
posted at https://developercommunity.visualstudio.com/content/problem/740540/helm3-setting-systemdebug-causes-helm-upgrade-pipe.html and they suggest updating the task to handle this situation.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 22 (8 by maintainers)
There are some issues in the helm project, which are related to this issue. https://github.com/helm/helm/issues/6009 https://github.com/helm/helm/issues/6461
I think this should either be fixed in the Azure DevOps task or, as a compromise, you can add an option to ignore STDERR as it is done in the Azure CLI task (see option “Fail on Standard Error”). Nevertheless i will create another issue in the helmet project. Somewhere it should be solved.
Still happening it seems, Azure DevOps…
Found tool in cache: helm 3.2.4 x64##[error]history.go:52: [debug] getting history for release xyz@hhellbusch , thanks for reporting this issue. I have checked in the fix for this(https://github.com/microsoft/azure-pipelines-tasks/pull/11473) and the fix should reach you in 2-3 weekes. Till then you can remove the --debug option as a workaround.