UPSTREAM: 52127: Fix deployment timeout reporting#16277
Merged
openshift-merge-robot merged 1 commit intoopenshift:masterfrom Sep 11, 2017
0xmichalis:cherry-pick
Merged
UPSTREAM: 52127: Fix deployment timeout reporting#16277openshift-merge-robot merged 1 commit intoopenshift:masterfrom 0xmichalis:cherry-pick
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
0xmichalis:cherry-pick
Conversation
If the previous condition has been a successful rollout then we shouldn't try to estimate any progress. Scenario: * progressDeadlineSeconds is smaller than the difference between now and the time the last rollout finished in the past. * the creation of a new ReplicaSet triggers a resync of the Deployment prior to the cached copy of the Deployment getting updated with the status.condition that indicates the creation of the new ReplicaSet. The Deployment will be resynced and eventually its Progressing condition will catch up with the state of the world. Signed-off-by: Michail Kargakis <mkargaki@redhat.com>
Contributor
|
/lgtm |
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kargakis, mfojtik The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
Contributor
Author
|
flake: #15988 |
Contributor
Author
|
/retest |
Contributor
|
Automatic merge from submit-queue |
Contributor
Author
|
/cherrypick release-3.6 |
|
@Kargakis: New pull request created: #17148 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If the previous condition has been a successful rollout then we
shouldn't try to estimate any progress. Scenario:
now and the time the last rollout finished in the past.
Deployment prior to the cached copy of the Deployment getting
updated with the status.condition that indicates the creation
of the new ReplicaSet.
The Deployment will be resynced and eventually its Progressing
condition will catch up with the state of the world.
Signed-off-by: Michail Kargakis mkargaki@redhat.com
Cherry-pick of kubernetes/kubernetes#52127
/assign @mfojtik @tnozicka
/area apps
/kind bug