On 26/10/2022 10:57, Stefan Kooman wrote:
On 10/25/22 17:08, Simon Oosthoek wrote:
At this point, one of noticed that a strange ip adress was mentioned;
169.254.0.2, it turns out that a recently added package (openmanage)
and some configuration had added this interface and address to
hardware nodes from Dell. For us, our single interface assumption is
now out the window and 0.0.0.0/0 is a bad idea in /etc/ceph/ceph.conf
for public and cluster network (though it's the same network for us).
Our 3 datacenters are on three different subnets so it becomes a bit
difficult to make it more specific. The nodes are all under the same
/16, so we can choose that, but it is starting to look like a weird
network setup.
I've always thought that this configuration was kind of non-intuitive
and I still do. And now it has bitten us :-(
Thanks for reading and if you have any suggestions on how to
fix/prevent this kind of error, we'll be glad to hear it!
We don't have the public_network specified in our cluster(s). AFAIK It's
not needed (anymore). There is no default network address range
configured. So I would just get rid of it. Same for cluster_network if
you have that configured. There I fixed it! ;-).
Hi Stefan
thanks for the suggestions!
I've removed the cluster_network definition, but retained the
public_network definition in a more specific way (list of the subnets
that we are using for ceph nodes). In the code it isn't entirely clear
to us what happens when public_network is undefined...
If you don't use IPv6, I would explicitly turn it off:
ms_bind_ipv6 = false
I just added this, it seems like a no brainer.
Cheers
/Simon
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
