Verified in 4.3.0-0.nightly-2020-05-18-043018 on top of RHOS_TRUNK-16.0-RHEL-8-20200506.n.2 OSP 16 compose. OSP 16 deployment with OVN backend. OCP 4.3 installation with Kuryr completed successfully. There are no 504 error responses to Prometheus metrics requests in the GUI "Home -> Overview" page. The metrics are retrieved correctly in "Monitoring -> Metrics" The metrics can be retrieved from the CLI as well: $ token=`oc sa get-token prometheus-k8s -n openshift-monitoring` $ openstack server list --all-projects | grep worker | 3c48285d-6ca0-46f1-bb15-a2de8bb3c9f0 | ostest-6jdcz-worker-ntlhg | ACTIVE | ostest-6jdcz-openshift=10.196.0.138 | ostest-6jdcz-rhcos | | | d6f35d22-0d8d-493d-bb07-dc2477d7245e | ostest-6jdcz-worker-flmq6 | ACTIVE | ostest-6jdcz-openshift=10.196.0.221 | ostest-6jdcz-rhcos | | | 0e8f4ba3-3fb4-4141-b3f5-3a4c25c5f3df | ostest-6jdcz-worker-7sb7x | ACTIVE | ostest-6jdcz-openshift=10.196.3.237 | ostest-6jdcz-rhcos | | $ oc -n openshift-monitoring exec -c prometheus prometheus-k8s-0 -- curl -k -H "Authorization: Bearer $token" 'https://10.196.0.138:9100/metrics' $ oc -n openshift-monitoring exec -c prometheus prometheus-k8s-0 -- curl -k -H "Authorization: Bearer $token" 'https://10.196.0.221:9100/metrics' $ oc -n openshift-monitoring exec -c prometheus prometheus-k8s-0 -- curl -k -H "Authorization: Bearer $token" 'https://10.196.3.237:9100/metrics' # HELP go_gc_duration_seconds A summary of the GC invocation durations. # TYPE go_gc_duration_seconds summary go_gc_duration_seconds{quantile="0"} 2.5085e-05 go_gc_duration_seconds{quantile="0.25"} 9.4514e-05 go_gc_duration_seconds{quantile="0.5"} 0.000147281 go_gc_duration_seconds{quantile="0.75"} 0.000250497 go_gc_duration_seconds{quantile="1"} 0.012237433 go_gc_duration_seconds_sum 0.105137669 go_gc_duration_seconds_count 146 # HELP go_goroutines Number of goroutines that currently exist. # TYPE go_goroutines gauge go_goroutines 6 # HELP go_info Information about the Go environment. # TYPE go_info gauge go_info{version="go1.12.12"} 1 # HELP go_memstats_alloc_bytes Number of bytes allocated and still in use. # TYPE go_memstats_alloc_bytes gauge go_memstats_alloc_bytes 2.286544e+06 # HELP go_memstats_alloc_bytes_total Total number of bytes allocated, even if freed. # TYPE go_memstats_alloc_bytes_total counter [...]
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-2020:2184