19.2.1 complains of all osd's being unreachable, as their public address
isn't in the public subnet. However, they all are within the subnet,
and are working normally as well.
It's embarrassing for the dashboard to glow red of a totally crippled
osd roster --- while all is working normally. This existed in the
previous, but was working prior to 19.
Detail:
Notice, for osd.0, the dashboard lists
public_addr
[fc00:1002:c7::44]:6807/4160993080
But, we have in the logs:
7/2/25 03:35 PM[ERR] osd.0's public address is not in
'fc00:1002:c7::/64' subnet
7/2/25 03:35 PM[ERR][ERR] OSD_UNREACHABLE: 27 osds(s) are not reachable
7/2/25 03:35 PM[ERR]Health detail: HEALTH_ERR 27 osds(s) are not reachable
However, as per the osd.0 attributes, the public address for osd.0 is
well inside the stated public subnet.
All the osd's are similarly configured, working, and held to be
unreachable at the same time, for the same reason.
Tell me there's a way to fix this without waiting a further half year....
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
