-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
deploymentconfigs when run iteratively [Conformance] should only deploy the last deployment #17581
Comments
/assign tnozicka |
this looks suspicious
and likely kubelet @bparees could you rebase your PR to pick up #17514 |
PRs are always merged on top of master before being tested. Rebasing my PR
wouldn't change anything in terms of testing.
Ben Parees | OpenShift
…On Dec 5, 2017 03:30, "Tomáš Nožička" ***@***.***> wrote:
this looks suspicious
Status:PodStatus{Phase:Pending,Conditions:[],Message:,Reason:,HostIP:,PodIP:,StartTime:<nil>,ContainerStatuses:[],QOSClass:BestEffort,InitContainerStatuses:[],},}]
and likely kubelet
@bparees <https://github.com/bparees> could you rebase your PR to pick up
#17514 <#17514>
Judging by age of your commits you are probably missing it
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#17581 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEvl3nmoln4VPr-1FXz27w3lZeKfvQ74ks5s9P86gaJpZM4Q1LAc>
.
|
this is bad
I'll continue searching for the cause tomorrow but the only place it creates a deployer is when the current status is |
Automatic merge from submit-queue (batch tested with PRs 18233, 18068, 18228, 18227). UPSTREAM: 58547: Send correct resource version for delete events from watch cache Backport of kubernetes/kubernetes#58547 Watch cache was returning incorrect (old) ResourceVersion on "deleted" events breaking informers that were going back in time. This fixes it. /assign @liggitt /cc @mfojtik Fixes #17581 #16003 and likely others
…e-fix-58547 Automatic merge from submit-queue (batch tested with PRs 18233, 18068, 18228, 18227). UPSTREAM: 58547: Send correct resource version for delete events from watch cache Backport of kubernetes#58547 Watch cache was returning incorrect (old) ResourceVersion on "deleted" events breaking informers that were going back in time. This fixes it. /assign @liggitt /cc @mfojtik Fixes openshift/origin#17581 openshift/origin#16003 and likely others Origin-commit: 042a63f8c1effc2fb911ce2cf494458872e9f8a3
…e-fix-58547 Automatic merge from submit-queue (batch tested with PRs 18233, 18068, 18228, 18227). UPSTREAM: 58547: Send correct resource version for delete events from watch cache Backport of kubernetes#58547 Watch cache was returning incorrect (old) ResourceVersion on "deleted" events breaking informers that were going back in time. This fixes it. /assign @liggitt /cc @mfojtik Fixes openshift/origin#17581 openshift/origin#16003 and likely others Origin-commit: 042a63f8c1effc2fb911ce2cf494458872e9f8a3
Automatic merge from submit-queue (batch tested with PRs 18233, 18068, 18228, 18227). UPSTREAM: 58547: Send correct resource version for delete events from watch cache Backport of kubernetes/kubernetes#58547 Watch cache was returning incorrect (old) ResourceVersion on "deleted" events breaking informers that were going back in time. This fixes it. /assign @liggitt /cc @mfojtik Fixes openshift/origin#17581 openshift/origin#16003 and likely others Origin-commit: 042a63f8c1effc2fb911ce2cf494458872e9f8a3 Kubernetes-commit: b1d49808af3db35be42e4b705953d656a21bc201
https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/17429/test_pull_request_origin_extended_conformance_crio/185/
The text was updated successfully, but these errors were encountered: