[Upgrade] After performing a rollback, upgraded (and rolled back) deployments don't start
See original GitHub issueThis is a…
[ ] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[X] Bug report
[ ] Documentation issue or request
The problem
I’m performing the rollback in upgrade_50_replace_template, where I’m appending exit 1
after update_version $tag
in replace_template::run()
.
After everything is rolled back, the deployments are scaled back to 1, but only those, that are not affected by upgrade (prometheus, oauthproxy, db [i’m not doing db migration for now]) are started back.
This is how it looks like after rollback:
The completed deployments in my case can’t be scaled up - when I scale them via oc or via web, it goes back to 0 after few seconds.
cc @rhuss @paoloantinori @dsimansk
Expected behavior
Screenshot
Request and Response Data
API Endpoints and Schemas
Tasks involved / Steps to Reproduce
Issue Analytics
- State:
- Created 5 years ago
- Comments:16 (8 by maintainers)
Top Results From Across the Web
Roll back a rolling upgrade - Atlassian Documentation
Roll back a rolling upgrade - AWS deployments · In the Stack Details screen, select Update Stack. · From the Select Template screen,...
Read more >Redeploy and roll back a deployment with CodeDeploy
CodeDeploy rolls back deployments by redeploying a previously deployed revision of an application as a new deployment. These rolled-back deployments are ...
Read more >How do you rollback deployments in Kubernetes? - Learnk8s
When you upgrade your Pods from version 1 to version 2, the Deployment creates a new ReplicaSet and increases the count of replicas...
Read more >Updating Watson Machine Learning assets following an ... - IBM
The rollback is a disruptive rollback. During the rollback process Watson Machine Learning assets and deployments will not be available for use.
Read more >Fix Forward Or Roll Back Code Changes - xMatters
When a rollout goes as planned, it looks like every other rollout: no errors to remediate, no disrupted services to restore, just new...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s a sample database we could probably remove it from next release and create a sample database template, like we do for AMQ, so not backing it up is perfectly OK with me.
@avano thanks for testing and the feedback !