On 17-10-2024 15:16, Nico Schottelius wrote:
Stefan Kooman <stefan@xxxxxx> writes:
On 16-10-2024 03:02, Harry G Coin wrote:
Thanks for the notion! I did that, the result was no change to the
problem, but with the added ceph -s complaint "Public/cluster
network defined, but can not be found on any host" -- with
otherwise totally normal cluster operations. Go figure. How can
ceph -s be so totally wrong, the dashboard reporting critical
problems -- except there are none. Makes me really wonder whether
any actual testing on ipv6 is ever done before releases are marked
'stable'.
As far as I know IPv6 is (still) not tested at all (but still IPv4
only).
How do you mean not tested? As in this particular release or in general?
In general. So no testing done in Teuthology. At least I was told this
during ceph developer meeting at Cephalocon 2023 in Amsterdam.
Just asking, because we are running IPv6 only ceph clusters since 2017
and I was wondering if we will be affected by something coming up soon.
We are running IPv6 only as well (also since 2017) and I know from
others that are running IPv6 only for way longer than that. An upgrade
to 19.2.x is likely to impact us in the same way. It appears to be
mostly cosmetical (ceph keeps working) but ceph -s reporting HEALTH_ERR
is kinda nasty, as we, and I guess many with us, rely on ceph -s for
health monitoring.
Gr. Stefan
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
