+++ This bug was initially created as a clone of Bug #1647707 +++ Description of problem: Same question with Bug 1646886, openshift-ansible 3.10 roles/openshift_facts/defaults/main.yml openshift_crio_var_sock is changed to /var/run/crio/crio.sock This caused 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-ansible-3.10.70-1 cri-o://1.10.6 metrics-cassandra-v3.10.66-4 metrics-hawkular-metrics-v3.10.66-4 metrics-schema-installer-v3.10.66-4 metrics-heapster-v3.10.66-2 How reproducible: Always Steps to Reproduce: 1. Deploy metrics 3.10 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: --- Additional comment from Junqi Zhao on 2018-11-08 02:58 EST ---
openshift-ansible-3.9.51-1 # openshift version openshift v3.9.51 kubernetes v1.9.1+a0ce1bc657 etcd 3.2.16 cri-o://1.9.14 metrics image version: v3.9.51 # grep -r "crio.sock" roles/container_runtime/defaults/main.yml:l_crio_var_sock: "{{ l_crio_use_new_var_sock | ternary('/var/run/crio/crio.sock', '/var/run/crio.sock') }}" roles/openshift_node/defaults/main.yml:l_crio_var_sock: "{{ l_crio_use_new_var_sock | ternary('/var/run/crio/crio.sock', '/var/run/crio.sock') }}"
PR:
PR: https://github.com/openshift/openshift-ansible/pull/11610
OCP 3.6-3.10 is no longer on full support [1]. Marking CLOSED DEFERRED. If you have a customer case with a support exception or have reproduced on 3.11+, please reopen and include those details. When reopening, please set the Target Release to the appropriate version where needed. [1]: https://access.redhat.com/support/policy/updates/openshift
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days