Bug 1298121
Summary: | Can't record NodeNotSchedulable/NodeSchedulable event when run command quickly | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | DeShuai Ma <dma> |
Component: | Node | Assignee: | Seth Jennings <sjenning> |
Status: | CLOSED NOTABUG | QA Contact: | Xiaoli Tian <xtian> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | unspecified | CC: | aos-bugs, gblomqui, haowang, jokerman, mmccomas |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-07-03 15:04:12 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
DeShuai Ma
2016-01-13 10:07:44 UTC
Its weird, somehow I am not able to see any events in origin now, still looking why the api server seems to be rejecting all events. E0203 11:02:32.658211 28129 event.go:188] Server rejected event '&api.Event{TypeMeta:unversioned.TypeMeta{Kind:"", APIVersion:""}, ObjectMeta:api.ObjectMeta{Name:"192.168.122.253.142f7a01c37a7f2d", GenerateName:"", Namespace:"default", SelfLink:"", UID:"", ResourceVersion:"", Generation:0, CreationTimestamp:unversioned.Time{Time:time.Time{sec:0, nsec:0, loc:(*time.Location)(nil)}}, DeletionTimestamp:(*unversioned.Time)(nil), DeletionGracePeriodSeconds:(*int64)(nil), Labels:map[string]string(nil), Annotations:map[string]string(nil)}, InvolvedObject:api.ObjectReference{Kind:"Node", Namespace:"", Name:"192.168.122.253", UID:"192.168.122.253", APIVersion:"", ResourceVersion:"", FieldPath:""}, Reason:"RegisteredNode", Message:"Node 192.168.122.253 event: Registered Node 192.168.122.253 in NodeController", Source:api.EventSource{Component:"controllermanager", Host:""}, FirstTimestamp:unversioned.Time{Time:time.Time{sec:63590112152, nsec:657100589, loc:(*time.Location)(0x51cd8c0)}}, LastTimestamp:unversioned.Time{Time:time.Time{sec:63590112152, nsec:657100589, loc:(*time.Location)(0x51cd8c0)}}, Count:1, Type:"Normal"}': 'Event "192.168.122.253.142f7a01c37a7f2d" is invalid: involvedObject.namespace: invalid value '', Details: not required for node' (will not retry!) I am able to reproduce the issue. Please note, I was able to reproduce it with origin/v1.1.1.1 tag as the latest origin master branch has issue as server is rejecting events from node. It seems that as far as one is as quick as under 5s, there wont be new events shown with oc get events. I looked into the code and it seems that it is working as expected. So right now it seems like "not a bug". The reason is that kubelet does not send/record events if it finds that there is not change in its current state (node.Spec.Unschedulable) and old state (oldNodeUnschedulable). If the change from Schedulable->Unschedulable->Schedulable is fast enough (every few seconds kubelet updates its status to api server ) that the state remain same Schedulable during this period, no event is generated. And thats why this behaviour. I am not sure it is worthwhile to change kubelet behaviour for this issue. So again I would say it sounds like "not a bug" right now. Please let me know if it makes sense and we can close this bug. See comment #6 |