Hide Forgot
Created attachment 1204782 [details] master_log_for_panic Description of problem: There is panic error appears in the master log during I was doing the adding/deleting operations on the project. Version-Release number of selected component (if applicable): openshift v1.4.0-alpha.0+b3ec794 kubernetes v1.4.0-beta.3+d19513f etcd 3.0.9 git commit: b3ec794bf74052d928b2927e93a32dba1738fd54 How reproducible: unknown Steps to Reproduce: 1. Setup multi-node env 2. Create multiple projects via user $ for i in {1..100}; do oc new-project userp$i ; done 3. Delete all the projects $ oc delete project -all 4. Run another adding/deleting project operation $ while true; do oc new-project userxx ; oc delete project userxx ; done 5. Watching the master log. Actual results: There is panic error appears in the master log. Expected results: Should not panic. Additional info: Master log and core dump file attached.
This looks more like a bug in upstream Kubernetes than OpenShift. My best guess is *namespace.DeletionTimestamp is causing the panic becuase the returned namespace object from retryOnConflictError() has been modified... Filed upstream: https://github.com/kubernetes/kubernetes/issues/33676 Should we close this as UPSTREAM resolution?
Thanks, that is ok for me.
I am curious if this was an HA setup?
Upstream PR: https://github.com/kubernetes/kubernetes/pull/34298
(In reply to Derek Carr from comment #5) > I am curious if this was an HA setup? For my testing, it is not HA env.
Origin PR: https://github.com/openshift/origin/pull/11632
origin pr merged.
Tested this issue on # openshift version openshift v3.4.0.19+346a31d kubernetes v1.4.0+776c994 etcd 3.1.0-rc.0 using always add/delete namespance step. no panic logs found on master logs. verified this bug.