-
Notifications
You must be signed in to change notification settings - Fork 790
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
All resources deleted from permanent environment #5281
Labels
Comments
/kind bug |
/priority critical-urgent |
jenkins-x-bot
added
the
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
label
Sep 2, 2019
/area multi-cluster |
2 tasks
pmuir
added
priority/critical
and removed
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
labels
Sep 5, 2019
Thank you for the PR. We will merge it when you are happy with it. Downgrading to |
Thanks, but for my pull request to work I need jenkins-x-charts/environment-controller#252 to be merged. EDIT: I rewrote the patch so it doesn't need jenkins-x-charts/environment-controller#252 |
jenkins-x-bot
pushed a commit
that referenced
this issue
Sep 8, 2019
Fixes #5281 Signed-off-by: Mårten Svantesson <Marten.Svantesson@ticket.se>
daveconde
pushed a commit
to daveconde/jx
that referenced
this issue
Apr 7, 2020
Fixes jenkins-x#5281 Signed-off-by: Mårten Svantesson <Marten.Svantesson@ticket.se>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
When running a remote environment set up according to https://jenkins-x.io/getting-started/multi-cluster/ a race condition exists that means all applications in the environment can be deleted.
Steps to reproduce the behavior
Expected behavior
Any changes are deployed
Actual behavior
All resources managed by the environment repo except pvc, configmaps and secrets got deleted.
Analysis
The step build-step-build-helm-apply in the second pipeline run that got started had applied it's changes just before the first pipeline runs build-step-build-helm-apply had come to "Removing Kubernetes resources from older releases using selector". So all resources from environment-sto-staging where deleted since they had gotten the version of the second pipeline run and thus mached the selector that was intended to fins old resources.
When using jenkins to deploy an environment the Jenkinsfile by default includes
preventing a race condition to occur. This is missing from the mechanism set up with the environment controller.
It might be relevant that the environment is configured to use helm template and not tiller.
Jx version
Environment controller use the image gcr.io/jenkinsxio/builder-maven:0.1.549
The output of
jx version
is:The text was updated successfully, but these errors were encountered: