#OCPBUGS-25331 | issue | 10 days ago | some events are missing time related infomration POST |
Issue 15675601: some events are missing time related infomration Description: Description of problem: {code:none} Some events have time related infomration set to null (firstTimestamp, lastTimestamp, eventTime) {code} Version-Release number of selected component (if applicable): {code:none} cluster-logging.v5.8.0{code} How reproducible: {code:none} 100% {code} Steps to Reproduce: {code:none} 1.Stop one of the masters 2.Start the master 3.Wait untill the ENV stabilizes 4. oc get events -A | grep unknown {code} Actual results: {code:none} oc get events -A | grep unknow default <unknown> Normal TerminationStart namespace/kube-system Received signal to terminate, becoming unready, but keeping serving default <unknown> Normal TerminationPreShutdownHooksFinished namespace/kube-system All pre-shutdown hooks have been finished default <unknown> Normal TerminationMinimalShutdownDurationFinished namespace/kube-system The minimal shutdown duration of 0s finished .... {code} Expected results: {code:none} All time related information is set correctly{code} Additional info: {code:none} This causes issues with external monitoring systems. Events with no timestamp will never show or push other events from the view depending on the sorting order of the timestamp. The operator of the environment has then trouble to see what is happening there. {code} Status: POST Resolution: Priority: Minor Creator: Roman Hodain Assigned To: Abu H Kashem | |||
#OCPBUGS-27075 | issue | 3 months ago | some events are missing time related infomration CLOSED |
Issue 15715205: some events are missing time related infomration Description: Description of problem: {code:none} Some events have time related infomration set to null (firstTimestamp, lastTimestamp, eventTime) {code} Version-Release number of selected component (if applicable): {code:none} cluster-logging.v5.8.0{code} How reproducible: {code:none} 100% {code} Steps to Reproduce: {code:none} 1.Stop one of the masters 2.Start the master 3.Wait untill the ENV stabilizes 4. oc get events -A | grep unknown {code} Actual results: {code:none} oc get events -A | grep unknow default <unknown> Normal TerminationStart namespace/kube-system Received signal to terminate, becoming unready, but keeping serving default <unknown> Normal TerminationPreShutdownHooksFinished namespace/kube-system All pre-shutdown hooks have been finished default <unknown> Normal TerminationMinimalShutdownDurationFinished namespace/kube-system The minimal shutdown duration of 0s finished .... {code} Expected results: {code:none} All time related information is set correctly{code} Additional info: {code:none} This causes issues with external monitoring systems. Events with no timestamp will never show or push other events from the view depending on the sorting order of the timestamp. The operator of the environment has then trouble to see what is happening there. {code} Status: CLOSED Resolution: Priority: Minor Creator: Rahul Gangwar Assigned To: | |||
#OCPBUGS-27074 | issue | 10 days ago | some events are missing time related infomration New |
Issue 15715202: some events are missing time related infomration Description: Description of problem: {code:none} Some events have time related infomration set to null (firstTimestamp, lastTimestamp, eventTime) {code} Version-Release number of selected component (if applicable): {code:none} cluster-logging.v5.8.0{code} How reproducible: {code:none} 100% {code} Steps to Reproduce: {code:none} 1.Stop one of the masters 2.Start the master 3.Wait untill the ENV stabilizes 4. oc get events -A | grep unknown {code} Actual results: {code:none} oc get events -A | grep unknow default <unknown> Normal TerminationStart namespace/kube-system Received signal to terminate, becoming unready, but keeping serving default <unknown> Normal TerminationPreShutdownHooksFinished namespace/kube-system All pre-shutdown hooks have been finished default <unknown> Normal TerminationMinimalShutdownDurationFinished namespace/kube-system The minimal shutdown duration of 0s finished .... {code} Expected results: {code:none} All time related information is set correctly{code} Additional info: {code:none} This causes issues with external monitoring systems. Events with no timestamp will never show or push other events from the view depending on the sorting order of the timestamp. The operator of the environment has then trouble to see what is happening there. {code} Status: New Resolution: Priority: Minor Creator: Rahul Gangwar Assigned To: Abu H Kashem |
Found in 0.00% of runs (0.00% of failures) across 266916 total runs and 11314 jobs (22.14% failed) in 107ms - clear search | chart view - source code located on github