-
Notifications
You must be signed in to change notification settings - Fork 57
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
Helm default flag --atomic leads to error when pulling latest #922
Comments
@renedupont - #opendevstack/ods-jenkins-shared-library/916 amongst many other things we pass the image tag already as helm value - and also the registry |
I think that would be the best solution long term. Using the BTW, when we discussed this yesterday I think we also concluded that the "atomic" behaviour might be applied to the old state, not the state after resources have been updated. It looks to me like #916 might fix that problem because it does not pause Helm deployments (but in turn it doesn't seem to auto-add the RM metadata labels anymore?). |
@michaelsauter - feel free to help... baking this was already kind of a hell of a ride :) |
@clemensutschig not sure I am of help at this stage, since you already made a lot of changes, and I would need to play a lot of catch-up. But maybe you want to walk me through the PR when it is closer to being done and we can cross-check a few things? There's also a few learnings about Helm that we had in the ODS pipeline BTW:
That wasn't to indicate that this should be put back in. More of a question. As noted #860 (which is actually somewhat related to what Rene encountered), I consider pausing/unpausing to be problematic and would rather avoid it if possible. |
@serverhorror did you test your PR against this behavior? Shall we close this one? |
Closing this as using git commit tag as image tag is by now the default way when using helm in ods. |
Describe the bug
We are using helm charts and in there, we configured to pull the latest image which we build earlier in the pipeline run:
As you can see here, the latest tag gets set AFTER
helm upgrade
was done in therollout stage
. Before that, we only have commit hash tag that was created in theimage build stage
.It is also important to know that we set here the helm default flags
--install
and--atomic
, where atomic does the following:The following happened: We did a pipeline run where we build successfully an image which was not able to run due to some misconfigurations. As a consequence, every pipeline run afterwards failed during helm upgrade due to
--atomic
not being successful and hence the latest tag was not set even though the image was successfully build. Since we are pullinglatest
, we never pulled the fixed image with the correct configuration but rather the one that failed in the past and we were basically stuck.We "fixed" it by uninstalling the helm release in openshift and then provide via the rollout stage new helm default flags where we just pass
--install
without--atomic
.Also, we had to remove the
DeploymentConfig
that was created from the provisioning process and which we don't use since we useDeployment
in our Helm chart.Another "workaround" that we discussed was to not pull latest and provide the commit sha tag to helm (via helmValues in jenkinsfile rolloutstage) and just pull that.
@michaelsauter @kuebler
The text was updated successfully, but these errors were encountered: