forked from rook/rook
The OSDs on PVCs were changing location in the CRUSH hierarchy after an operator restart due to the location property not being re-discovered on the OSD daemon. Since OSDs on PVCs do not run the prepare pod again to discover this property, the operator must read it off the existing osd deployment. The operator was reading other properties, but now will read the location as well. Signed-off-by: Travis Nielsen <tnielsen@redhat.com>