We now have a more recent ceph-deploy 1.5.9 in 5.1 so this problem should disappear. Since it's a low priority bug it will not be backported to stable release series.
We now have a more recent ceph-deploy 1.5.9 in 5.1 so this problem should disappear. Since it's a low priority bug it will not be backported to stable release series.