Upstream PR: https://github.com/openshift/openshift-ansible/pull/8596
Since Bug 1589023, openshift-router target shows "no route to host", see the attached picture Change back to MODIFIED openshift-ansible-3.9.41-1.git.0.4c55974.el7.noarch # openshift version openshift v3.9.41 kubernetes v1.9.1+a0ce1bc657 etcd 3.2.16
Created attachment 1477792 [details] "no route to host" error for router targets
@Simon From the attached picture the openshift-router target is http://172.16.120.91:1936/metrics, should it be use https protocol https://172.16.120.91:1936/metrics? since 3.10, I see the router target is using https protocol
Please ignore Comment 4 and Comment 5, it is another issue, I think we could close this defect, following is my reason # get token token=`oc sa get-token prometheus -n openshift-metrics`, then oc rsh {router-pod}, and use the token from the previous step and run command curl -k -H "Authorization: Bearer $token" http://{router_ip}:1936/metrics we can get the prometheus output, see the attached file
Created attachment 1477811 [details] router prometheus output
According to the previous attachment, it is a multinode cluster and it is probably a firewall issue as described in https://bugzilla.redhat.com/show_bug.cgi?id=1552235
Per Comment 6 - Comment 8, problem mentioned in this defect is fixed, set to VERIFIED
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-2018:2549