Bug 1931668

Summary: [sig-api-machinery][Feature:APIServer][Late] kubelet terminates kube-apiserver gracefully
Product: OpenShift Container Platform Reporter: Gabe Montero <gmontero>
Component: NodeAssignee: Ryan Phillips <rphillips>
Node sub component: Kubelet QA Contact: Sunil Choudhary <schoudha>
Status: CLOSED DUPLICATE Docs Contact:
Severity: unspecified    
Priority: unspecified CC: aos-bugs, mfojtik, xxia
Version: 4.8   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
[sig-api-machinery][Feature:APIServer][Late] kubelet terminates kube-apiserver gracefully
Last Closed: 2021-02-23 13:43:18 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 Gabe Montero 2021-02-22 21:50:23 UTC
test:
[sig-api-machinery][Feature:APIServer][Late] kubelet terminates kube-apiserver gracefully 

is failing frequently in CI, see search results:
https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5Bsig-api-machinery%5C%5D%5C%5BFeature%3AAPIServer%5C%5D%5C%5BLate%5C%5D+kubelet+terminates+kube-apiserver+gracefully


https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_oc/742/pull-ci-openshift-oc-master-e2e-metal-ipi-ovn-ipv6/1363925016005054464


fail [github.com/onsi/ginkgo.0-origin.0+incompatible/internal/leafnodes/runner.go:64]: kube-apiserver didn't terminate by itself during the graceful termination period: v1.Event{TypeMeta:v1.TypeMeta{Kind:"", APIVersion:""}, ObjectMeta:v1.ObjectMeta{Name:"kube-apiserver-master-1.ostest.test.metalkube.org.166629e96c60a336", GenerateName:"", Namespace:"openshift-kube-apiserver", SelfLink:"", UID:"85fec414-0356-45bc-9b54-01a22ba0eee3", ResourceVersion:"18735", Generation:0, CreationTimestamp:v1.Time{Time:time.Time{wall:0x0, ext:63749620398, loc:(*time.Location)(0x95105e0)}}, DeletionTimestamp:(*v1.Time)(nil), DeletionGracePeriodSeconds:(*int64)(nil), Labels:map[string]string(nil), Annotations:map[string]string(nil), OwnerReferences:[]v1.OwnerReference(nil), Finalizers:[]string(nil), ClusterName:"", ManagedFields:[]v1.ManagedFieldsEntry{v1.ManagedFieldsEntry{Manager:"watch-termination", Operation:"Update", APIVersion:"v1", Time:(*v1.Time)(0xc000cdeb00), FieldsType:"FieldsV1", FieldsV1:(*v1.FieldsV1)(0xc000cdec60)}}}, InvolvedObject:v1.ObjectReference{Kind:"Pod", Namespace:"openshift-kube-apiserver", Name:"kube-apiserver-master-1.ostest.test.metalkube.org", UID:"", APIVersion:"v1", ResourceVersion:"", FieldPath:""}, Reason:"GracefulTerminationTimeout", Message:"kube-apiserver did not terminate within 2m15s", Source:v1.EventSource{Component:"apiserver", Host:"master-1.ostest.test.metalkube.org"}, FirstTimestamp:v1.Time{Time:time.Time{wall:0x0, ext:63749620398, loc:(*time.Location)(0x95105e0)}}, LastTimestamp:v1.Time{Time:time.Time{wall:0x0, ext:63749620398, loc:(*time.Location)(0x95105e0)}}, Count:1, Type:"Warning", EventTime:v1.MicroTime{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, Series:(*v1.EventSeries)(nil), Action:"", Related:(*v1.ObjectReference)(nil), ReportingController:"", ReportingInstance:""}. This is a bug in kube-apiserver. It probably means that network connections are not closed cleanly, and this leads to network I/O timeout errors in other components.

Comment 1 Gabe Montero 2021-02-23 13:43:18 UTC

*** This bug has been marked as a duplicate of bug 1931624 ***