Ceph » RADOS

An IPv6 link-local scoped address is not currently parseable since it contains a "%<interface name>" suffix in the address (e.g. fe80::219:99ff:fe9e:3a86%eth0). This was discovered because an RBD lock for that client IP address was recorded in the lock.rbd_lock xattr but attempting to manually remove the lock failed:

[root@vm2003 images1]# rbd -p rbd_vms_hdd lock list fpi_server02
There is 1 exclusive lock on this image.
Locker         ID                  Address                                      
client.1195723 auto 93921602220416 [fe80::219:99ff:fe9e:3a86%eth0]:0/1200385089 

[root@vm2003 images1]# rbd -p rbd_vms_hdd lock rm fpi_server02 "auto 93921602220416" client.1195723
rbd: releasing lock failed: (22) Invalid argument
2018-07-09 20:45:19.080543 7f6c2c267d40 -1 librados: unable to parse address [fe80::219:99ff:fe9e:3a86%eth0]:0/1200385089
2018-07-09 20:45:19.080555 7f6c2c267d40 -1 librbd: unable to blacklist client: (22) Invalid argument

The optional scope should probably be ignored in entity_addr_t since "inet_pton" ignores it. Additionally, in this particular case the client entity_addr_t was actually the incorrect address to provide to the MONs/OSDs since it was:

eth0 is part of bond0 which is a vlan trunk. Bond0.X is attached to brX which has an ULA-prefix for the ceph cluster.
Eth0 has no address itself. In this case this must mean, the address has been carried down to the hardware interface.