Get OSD bootstrap key on the current node if possible
Get OSD bootstrap key on the current node if possible

When deploying monitor and OSD daemons on the same node, it is
possible to retrieve the OSD bootstrap key from the node itself
(if the monitor recipe has already been applied), instead of
relying on a search in Chef for existing monitors.

This change also serves as a workaround when monitor and OSD
daemons are being installed on the first node of the cluster and,
for some reason, chef-client doesn't converge at the first attempt.
Without this change, running chef-client a second time, the node
might not be found with the Chef search.

osuosl-cookbooks/ceph-cookbook,ceph/ceph-cookbook,osuosl-cookbooks/ceph-cookbook,ncerny/ceph-cookbook,osuosl-cookbooks/ceph-cookbook,nareiber/ceph-cookbook,tas50/ceph-cookbook,tas50/ceph-cookbook,tas50/ceph-cookbook,sandoracs/ceph-cookbook,klamontagne/ceph-cookbook,nareiber/ceph-cookbook,sandoracs/ceph-cookbook,sandoracs/ceph-cookbook,ncerny/ceph-cookbook,nareiber/ceph-cookbook,ncerny/ceph-cookbook,klamontagne/ceph-cookbook,ceph/ceph-cookbook,klamontagne/ceph-cookbook,ceph/ceph-cookbook