Description of problem: ConnectivityOutageDetected and ConnectivityRestored events do not always have a related object that helps determine where the problem is occurring. For example, the events from kube-apiserver pod sometimes list the namespace as the related object, which is not as helpful as listing the node, which would help narrow the source to the pod running on that node. Events from the openshift-apiserver list the apiserver deployment, which itself offers no insight into which of the pods is having the connectivity issue.
I will normalize the connectivity events to always specify the source pod's node as the relatedObject. While it might seem that the pod name is a more natural fit for this purpose, the auto-generated pod names that result from a deployment do not offer a hint of which node is experiencing the issue, especially if the pod has been re-created in the meantime.
Tested in 4.6.0-0.nightly-2020-09-24-095222: $ oc get event -n openshift-kube-apiserver -o yaml Saw involvedObject has node name for ConnectivityOutageDetected and ConnectivityRestored: involvedObject: kind: Node name: ip-10-0-154-169.ap-northeast-1.compute.internal namespace: openshift-kube-apiserver uid: 22be2d53-eb65-4309-9ace-7bb4c8cefb5f kind: Event ... reason: ConnectivityOutageDetected ... involvedObject: kind: Node name: ip-10-0-154-169.ap-northeast-1.compute.internal namespace: openshift-kube-apiserver uid: 22be2d53-eb65-4309-9ace-7bb4c8cefb5f kind: Event ... reason: ConnectivityRestored Same for OAS: $ oc get event -n openshift-apiserver -o yaml involvedObject: kind: Node name: ip-10-0-154-169.ap-northeast-1.compute.internal namespace: openshift-apiserver uid: 22be2d53-eb65-4309-9ace-7bb4c8cefb5f kind: Event ... reason: ConnectivityRestored
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 (OpenShift Container Platform 4.6 GA Images), 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-2020:4196