-
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
Cache mutation bug #15324
Comments
Note there are two other failures in that run also, that make it appear as if the server went away:
probably unrelated, but also probably rebase related? |
seems like upstream bug? |
Yes, but it will block our CI until it's fixed. |
Same run? The cache mutation kills the server. |
attempt to fix this: #15328 |
Yeah same run.
Ben Parees | OpenShift
…On Jul 19, 2017 7:17 AM, "David Eads" ***@***.***> wrote:
probably unrelated, but also probably rebase related?
Same run? The cache mutation kills the server.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#15324 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEvl3jJWxG-5EANISjtTWyiOZYXvriVTks5sPeXKgaJpZM4OcM9w>
.
|
weird, the diff showed kind and apiVersion fields got populated, and nothing else changed... I bet passing an object to an encoder sets those fields. |
Assigned you since you have a pull. |
Automatic merge from submit-queue (batch tested with PRs 49328, 49285, 49307, 49127, 49163) fix mutation in statefulset sync Original issue: openshift/origin#15324 Seems like something inside `UpdateStatefulSet` mutates the StatefulSet. We might need to dig deeper to find the exact location where the non-copy mutation happens.
This is fixed and @mfojtik said he will open a follow-up issue upstream to track investigation on this. |
https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin/3256/
Cache mutations are not flakes. They are P0 bugs and you found one. Open it up!
was run against post-rebase code.
The text was updated successfully, but these errors were encountered: