OCS/ODF How to find the disk device associated to an OSD pod when using LSO

Issue

• Sometimes on situations like:

  • osd pod that is using PV from LSO, fails to start with error log

  failed to read label for /var/lib/ceph/osd/ceph-0/block: (2) No such file or directory
  

  • on the OCS node device paths are deleted due to some bug , for example OSD pods go offline due to bad 'google-' symlinks when using ODF with LSO

  ...we may need to find the associated device file name that is used by an osd pod.

• On this document we have as an example osd.0 that should start on OCS node worker2 , then will find the associated device and then will confirm that is the correct one.

  osd.0 fail to start on worker2
  
  rook-ceph-osd-0-565cxxxxxx-yyyyy                                 0/2    Pending  0         17h    10.x.x.2    worker2