Bug 2231068

Summary:	ceph-exporter scrapes failing on multi-homed server
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	avan <athakkar>
Component:	Ceph-Dashboard	Assignee:	Nizamudeen <nia>
Status:	ON_QA ---	QA Contact:	Sayalee <saraut>
Severity:	high	Docs Contact:	Anjana Suparna Sriram <asriram>
Priority:	unspecified
Version:	6.1	CC:	ceph-eng-bugs, cephqe-warriors, saraut, tserlin, vereddy
Target Milestone:	---
Target Release:	6.1z2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ceph-17.2.6-110.el9cp	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description avan 2023-08-10 12:46:24 UTC

Description of problem:

ceph-exporter only binds to a specific interface. All other monitoring related daemons bind to all (grafana, prometheus, alertmanager and node-exporter)

In my test environment with a multi-homed server, the exporter bound to one address but the prometheus scrape target (defined within cephadm) was set to a different address on the same machine. As a result all scrapes fail.

If ceph-exporter adopts the --addrs 0.0.0.0 parameter, this issue can be avoided and it aligns to the same principles as the other monitoring daemons.