What's the behaviour of Linux with multiple disks with clashing partition labels?

I am running CoreOS with the root filesystem on a particular SSD device (say /dev/sda) and I want to install Flatcar Linux onto a different SSD device (say /dev/sdb). The reason I am doing this is that /dev/sdb is smaller so I want to turn /dev/sda into a device just for external storage. CoreOS labels the root filesystem partition ROOT, (i.e. /dev/disk/by-partlabel/ROOT is a symlink to the root partition on /dev/sda). However, when I install Flatcar Linux onto /dev/sdb, I will get the same thing (i.e. the root partition on /dev/sdb will also be labelled ROOT -- I could change this of course, but my OCD wants to stick to the same value specified in the documentation ). I plan to change the BIOS settings to prioritise /dev/sdb over /dev/sda when booting so that Flatcar Linux boots by default, but will there be an issue with these clashing partlabels? I would hope that udev (which creates these symlinks as far as I know) would see that the /dev/disk/by-partlabel/ROOT symlink already exists (and refers to the root partition on /dev/sdb) and skips creating the symlink for /dev/sda, but is that actually what happens?