Bug 1718879

Summary:	Cache mutation detected in CI
Product:	OpenShift Container Platform	Reporter:	Mo <mkhan>
Component:	kube-apiserver	Assignee:	Mo <mkhan>
Status:	CLOSED ERRATA	QA Contact:	Xingxing Xia <xxia>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	4.2.0	CC:	aos-bugs, jokerman, mfojtik, mmccomas, sttts
Target Milestone:	---
Target Release:	4.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-16 06:31:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mo 2019-06-10 13:23:13 UTC

Description of problem:

Something is modifying the KAS shared cache when it should not.

A: 

B: 


panic: cache *apiextensions.CustomResourceDefinition modified

goroutine 2598 [running]:
github.com/openshift/origin/vendor/k8s.io/client-go/tools/cache.(*defaultCacheMutationDetector).CompareObjects(0xc001d1cc00)

https://storage.googleapis.com/origin-ci-test/pr-logs/pull/22904/pull-ci-openshift-origin-master-cmd/6230/artifacts/cmd/logs/kube-apiserver.log

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Mo 2019-07-23 00:46:29 UTC

After I found the bug, Stefan fixed it in https://github.com/openshift/origin/pull/23142

I have various followups to make this easier to debug in the future, but this bug is fixed.

Comment 3 Stefan Schimanski 2019-07-23 09:38:31 UTC

I don't think we can easily test this in a normal cluster. It requires some internal cache detection logic to uncover (that's what @Mo did). Usually you won't notice as a user that there is an issue. Yet, there is a chance for inconsistent behavour. That's why we have to fix it.

Comment 6 errata-xmlrpc 2019-10-16 06:31:56 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2922