-
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
Rollout superseding an in progress rollout gets stuck #3331
Comments
|
More data: after talking with @zachaller we thought one possibility was rollbackWindow setting (i was using that, but he was not - and unable to reproduce) So, did some more testing. It gets weirder. :D
Rev 1 - deploys ok
set to 50% weight, 2 replicas
|
The changes made in the #3077 is adding an deeper check to validate the service selecton. |
Fixed by #3354 |
Checklist:
Describe the bug
Rollout is currently live. (Rev1)
Start a new Rollout. (Rev2)
While this rollout is in progress, start another Rollout (Rev 3)
The Rollout Rev 3 gets 'stuck' - doesn't progress.
The Rollout Rev 2 is also stuck - doesn't get spun down.
To Reproduce
(assuming you already have a stable rollout in cluster - Rev 1)
Start a rollout. (Rev 2)
While that rollout is progressing, start another rollout. (Rev 3)
Expected behavior
Rev 2 should be cancelled, and spin down. Then Rev 3 should start spinning up.
Screenshots
Version
Tested with 1.6.4 and 1.6.5
This is a regression, as I tested with 1.5.1 before upgrading to 1.6.4/5
With 1.5.1 this bug didn't happen.
The rollout is a basic canary rollout. No traffic routing.
Workaround/How to get out of this bad state
If you find yourself in this situation, you can get unstuck by:
Abort the rollout. This will put you back into the Stable configuration. Then hit Retry. This will start the Rollout.
So going with the above example of my repro steps Rev 3 would then proceed as normal.
Logs
So overall at this point, the rollout is stuck.
I'd be interested in pairing with someone to fix this.
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: