I've attache a work around path in the bug, but it is an ugly work around. That said, I noticed some strange behavior. Links format are completely different to how the links format is handled for scsi devices:
For example: 'sdb' we see two links:
Checking that path [/dev/sdb] and is same as link [wwn-0x600508b1001c29aef10ecd96f5df2342]
Checking that path [/dev/sdb] and is same as link [scsi-3600508b1001c29aef10ecd96f5df2342]
For 'nvme' we also see two with completely different format:
Checking that path [/dev/nvme0n1] and is same as link [nvme-nvme.8086-43564d44343334353030424e34303041474e-494e54454c205353445045444d453430304734-00000001]
Checking that path [/dev/nvme0n1] and is same as link [nvme-INTEL_SSDPEDME400G4_CVMD434500BN400AGN]
I've attache a work around path in the bug, but it is an ugly work around. That said, I noticed some strange behavior. Links format are completely different to how the links format is handled for scsi devices:
For example: 'sdb' we see two links:
Checking that path [/dev/sdb] and is same as link [wwn-0x600508b1 001c29aef10ecd9 6f5df2342] 001c29aef10ecd9 6f5df2342]
Checking that path [/dev/sdb] and is same as link [scsi-3600508b1
For 'nvme' we also see two with completely different format:
Checking that path [/dev/nvme0n1] and is same as link [nvme-nvme. 8086-43564d4434 3334353030424e3 4303041474e- 494e54454c20535 3445045444d4534 30304734- 00000001] SSDPEDME400G4_ CVMD434500BN400 AGN]
Checking that path [/dev/nvme0n1] and is same as link [nvme-INTEL_