Ceph » mgr » Dashboard

Fix is pretty straightforward...submitted a PR https://github.com/ceph/ceph/pull/42716

Duplicate of https://tracker.ceph.com/issues/52117. Already fixed.

Avan Thakkar wrote:

Duplicate of https://tracker.ceph.com/issues/52117. Already fixed.

Not sure why this was closed as duplicate... issue 52117 is related to the dashboard URL, and this issue is on the address dashboard is binding to (as in it is not binding to the wildcard address).

Please re-open (I don't seem to be able to update the status...)

I typed a big bug report to find out this bug report covers the same problem, just different symptoms

Perhaps my findings are of some use, I'll paste it here:

Description of problem¶

After upgrade Octopus -> Pacific I found my ceph-mgr processes listening on <node-ip>:<port> instead of *:<port>.

Ceph Mgr Dashboard Documentation states default is :: if mgr/dashboard/server_addr is left unconfigured but this is not the case.

https://docs.ceph.com/en/latest/mgr/dashboard/?highlight=backfill#:~:text=If%20no%20specific%20address%20has%20been%20configured%2C%20the%20web%20app%20will%20bind%20to%20%3A%3A%2C%20which%20corresponds%20to%20all%20available%20IPv4%20and%20IPv6%20addresses.

Environment¶

• ceph version string: 16.2.5
• Platform (OS/distro/release): Ubuntu 20.04
• Cluster details (nodes, monitors, OSDs): 3 nodes, 3 mons, 3 mgrs, 4 cephfs, 20 OSDs
• Did it happen on a stable environment or after a migration/upgrade?: Problem found after upgrade from Ceph 15.2.14
• Browser used (e.g.: Version 86.0.4240.198 (Official Build) (64-bit)): N/A

How reproducible¶

Steps:

1. Leave `mgr mgr/dashboard/server_addr` config default, documentation states the ceph-mgr listener will be ::

Actual results¶

ceph-mgr listener is <ip-address>:<port>

~
root @ node2 # ceph config get mgr mgr/dashboard/server_addr
::

~
root @ node2 # ceph config get mgr mgr/dashboard/server_port
7080

~
root @ node2 # ss -tlpn | grep ceph-mgr
LISTEN 0      512      [2001:db8:2000:8a:67:616e:6573:6861]:6800           [::]:*                      users:(("ceph-mgr",pid=2997269,fd=24))
LISTEN 0      512      [2001:db8:2000:8a:67:616e:6573:6861]:6801           [::]:*                      users:(("ceph-mgr",pid=2997269,fd=28))
LISTEN 0      5        [2001:db8:2000:8a:67:616e:6573:6861]:9283           [::]:*                      users:(("ceph-mgr",pid=2997269,fd=43))
LISTEN 0      5        [2001:db8:2000:8a:67:616e:6573:6861]:7080           [::]:*                      users:(("ceph-mgr",pid=2997269,fd=56))

Expected results¶

A listener on [::]:<server_port>, as is the default stated by the documentation

Additional info¶

I've tried configuring `mgr/dashboard/server_addr` with alternative addresses, like such

ceph config set mgr mgr/dashboard/server_addr '::'
ceph config set mgr mgr/dashboard/server_addr '[::]'
ceph config set mgr mgr/dashboard/server_addr '*'

The first doesn't do what it is supposed to do (This is also the default). It gives you a listener on <ip-address>:<port>

The second option makes the mgr crash at start-up, obviously invalid. (gaierror(-2, 'Name or service not known'))

The last also makes the mgr crash at start-up (OSError("No socket could be created -- (('0.0.0.0', 7080): [Errno 2] Name or service not known) - (('::', 7080, 0, 0): [Errno -2] Name or service not known)",))

My other Ceph Octopus cluster has `mgr/dashboard/server_addr` unconfigured and here all ceph-mgr processes are listening on *, but more specifically so is the ceph-mgr process for the dashboard. So it seems like a recent change.

root @ mon1.ceph2 # ss -tlpn | grep ceph-mgr
LISTEN   0        5                             *:7443                 *:*       users:(("ceph-mgr",pid=1818,fd=27))
LISTEN   0        5                             *:9283                 *:*       users:(("ceph-mgr",pid=1818,fd=24))