Bug #39711
closed"unable to find any IPv4 address in networks <ipv6-network>" after upgrade to nautilus on osd and mds
0%
Description
After upgrading our OSDs to Nautilus they refused to start logging
May 11 10:06:19 ceph-1 ceph-osd[8777]: 2019-05-11 10:06:19.131 7f5dca047d80 -1 unable to find any IPv4 address in networks '2001:abc:2100:400::/54' interfaces '' May 11 10:06:19 ceph-1 ceph-osd[8777]: 2019-05-11 10:06:19.131 7f5dca047d80 -1 Failed to pick public address. May 11 10:06:19 ceph-1 systemd[1]: ceph-osd@10.service: main process exited, code=exited, status=1/FAILURE May 11 10:06:19 ceph-1 systemd[1]: Unit ceph-osd@10.service entered failed state. May 11 10:06:19 ceph-1 systemd[1]: ceph-osd@10.service failed. May 11 10:06:19 ceph-1 systemd[1]: ceph-osd@10.service holdoff time over, scheduling restart. May 11 10:06:19 ceph-1 systemd[1]: Stopped Ceph object storage daemon osd.10.
Since the cluster is IPv6 only it doesn't really make sense to obtain an IPv4 address. Before the upgrade the OSDs were starting just fine using the default IPv6 address. Now we had to bind them manually in the ceph.conf which is pretty ugly.
Later during the upgrade we faced the same issue with MDS and could also "fix" it by pinning the IP-Address in the ceph.conf.
Updated by Nathan Cutler almost 5 years ago
- Project changed from Ceph to Messengers
Updated by Dominik Csapak almost 5 years ago
i stumbled across the same issue and found that (seemingly only for osds) ms_bind_to_ipv6 does not disable ms_bind_to_ipv4
so another method would be to set ms_bind_to_ipv4 to false in the global section
Updated by Dominik Csapak almost 5 years ago
it is of course ms_bind_ipv6 and ms_bind_ipv4 (without the to )
Updated by Thore K almost 5 years ago
Thanks for sharing. This solves my issue and seems to be related to http://docs.ceph.com/docs/nautilus/rados/configuration/msgr2/#bind-configuration-options
Now what kind of issue is this?
Is it intended behaviour to prefer legacy IP and users of IP should just be warned about this (in the upgrade guide), or shouldn't this issue occur at all?
Updated by Matthew Oliver over 3 years ago
- Pull request ID set to 36536
I put this PR together which addresses this issue.
Updated by Kefu Chai over 3 years ago
- Is duplicate of Bug #46845: Newly orchestrated OSD fails with 'unable to find any IPv4 address in networks '2001:db8:11d::/120' with ms_bind_ipv6=true added
Updated by Daniel Pivonka over 2 years ago
- Related to Bug #52867: pick_address.cc prints: unable to find any IPv4 address in networks 'fd00:fd00:fd00:3000::/64' interfaces added