[RHOCP 4] Prometheus target 'serviceMonitor/openshift-metallb-system/monitor-metallb-controller/0' has a error message 'server returned HTTP status 502 Bad Gateway'
Issue
-
Default
Metallb Operator
setup has no issue andPrometheus target
for theController
isUp
. The issue is observed when trying to host thespeaker
on specific infra nodes,speaker
pods are scheduled on theinfra nodes
with the specific taints applied, butPrometheus target
has a failure with below error:server returned HTTP status 502 Bad Gateway
-
kube-rbac-proxy
container in the metallbcontroller
pod shows the below error:$ oc logs controller-xxxx -c kube-rbac-proxy -n metallb-system http: proxy error: dial tcp 10.xx.xx.xx:7472: connect: connection refused
Environment
- Red Hat OpenShift Container Platform (RHOCP)
- 4
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.