@Santosh Pillai <sapillai> ----> This issue was associated with one Nokia CloudRAN Support Case where the reported OCP version was ODF 4.10
OCP 4.10 is an important release for several Nokia CloudRAN programmes and they would expect this issue to fixed in ODF 4.10 but also ODF 4.11 and ODF 4.12
There is no Target release Specified for this Bugzilla ?

Nokia need this issue fixed in ODF 4.10 ODF 4.11 and ODF 4.12  
Can you clarify please ODF Engineering Fix Targets

Colum Gaynor - Senior Partner Success Manager, Global Nokia Account

I would go one step back to Local Storage Operator (that creates the PVs on these disks). 
When the system reboots, the multipath is not guaranteed to be same. Like, if it was /dev/dm-1 before reboot, it can be /dev/dm-2 after reboot. 
If the device have a stable /dev/disk/by-id/ then LSO should use them instead. Then even if the device name changes on reboot, symlink will keep pointing to the /dev/disk/by-id/. 

Currently I see that customer is using /dev/disk/by-path. 
```
  storageClassDevices:
  - devicePaths:
    - /dev/disk/by-path/pci-0000:81:00.0-sas-phy2-lun-0
    - /dev/disk/by-path/pci-0000:81:00.0-sas-phy3-lun-0
    storageClassName: localblock
    volumeMode: Block
```
So I would just to use the `/dev/disk/by-id` in the LocalVolume (or use LocalVolumeSet) and see if that fixes the upgrade issue.

any new update on this?

*** Bug 2167651 has been marked as a duplicate of this bug. ***