Storage device names, such as /dev/sdX, are inconsistent between boots

Issue

• Storage device names (e.g., /dev/sdX or /dev/nvmeXnY) change after a reboot or path failover/recovery.
• The system had assigned /dev/sdn device name to the SAN LUN, but after a kernel update this name was changed to /dev/sdk, is this expected behavior?
• I am unable to rename the /dev/dm-XX device on the server.
• The /dev/sdx name associated with a virtual disk change assigned order upon repeated booting cycles.
• The /dev/sdx name associated with a storage disk changed the assigned value across reboots.
• The device names associated with a storage disk are non-persistent across boots. The same name references different physical disks on different boot up sessions.
• The device names associated with a storage disk are non-persistent across the other nodes in the cluster. The same name references different disks on different nodes.
• On a system with multiple types of HBAs, it is possible for the device file name /dev/sdX to change across reboots. Seems to happen more often when mixing SAN storage and/or with other types of storage.
• Using /dev/sdX names is leading to data loss (mkfs wrong drive), or information leaks (using wrong drive in virtual machines) and other critical problems.
• Oracle ASM disk paths are incorrectly mapped or changed after a server reboot.