This bug was caused by ceph-deploy upgrade to 1.5.x in 5.1, it wasn't present in 5.0.x where ceph-deploy is still 1.2.x.
This bug was caused by ceph-deploy upgrade to 1.5.x in 5.1, it wasn't present in 5.0.x where ceph-deploy is still 1.2.x.