Created attachment 1502317 [details] network metrics graph could be shown - kube-system Description of problem: This defect is from https://bugzilla.redhat.com/show_bug.cgi?id=1631300#c20 There are 3 namespaces(kube-system, openshift-node, openshift-sdn) could show network metrics graph, but it is empty for other namespace. See the attached pictures. Workaround is restart atomic-openshift-node on every nodes, then network metrics graph will be shown. Version-Release number of selected component (if applicable): # openshift version openshift v3.11.39 metrics-cassandra-v3.11.16-5 metrics-hawkular-metrics-v3.11.16-5 metrics-heapster-v3.11.16-3 metrics-schema-installer-v3.11.16-4 cri-o://1.11.8 How reproducible: Always Steps to Reproduce: 1. Deploy metrics 3.11 in CRI-O env 2. 3. Actual results: There are 3 namespaces(kube-system, openshift-node, openshift-sdn) could show network metrics graph, but it is empty for other namespace. Expected results: Should show network metrics graph for all namespaces Additional info:
Created attachment 1502318 [details] There is notnetwork metrics graph - openshift-infra
Created attachment 1502319 [details] network metrics graph could be shown after restarting atomic-openshift-node.service - openshift-infra
Note: CRI-O sockert is changed to /var/run/crio/crio.sock from unix:///var/run/crio/crio.sock we can see the warning info, it is recommend us to use format "unix:///var/run/crio/crio.sock". # master-logs etcd etcd W0925 07:16:36.726552 19184 util_unix.go:75] Using "/var/run/crio/crio.sock" as endpoint is deprecated, please consider using full url format "unix:///var/run/crio/crio.sock".
Created attachment 1579226 [details] ansible logs
Fix for l_kubelet_node_name issue: PR: https://github.com/openshift/openshift-ansible/pull/11699
Created attachment 1582082 [details] empty network diagram -- openshift-infra
Upstream fix https://github.com/google/cadvisor/pull/2284
Related origin issue https://github.com/openshift/origin/issues/23492
cherry-pick to cadvisor fork https://github.com/openshift/google-cadvisor/pull/7
origin bump https://github.com/openshift/origin/pull/23585
Brian, Fix tracking for this issue for 3.11.z via https://bugzilla.redhat.com/show_bug.cgi?id=1741679
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, 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-2019:2922