Hi! I have laptop with UEFI. Tumbleweed already was installed on it (by me) and all was fine.
Recently I've bought SSD and installed it into this laptop. So I decide to install OS on SSD to take speed advantage.
I've done new Tumbleweed installation to SSD from USB-stick, but I want to keep previous OS (TW too) on HDD for some time.

Now, when laptop boots, I see GRUB menu where default boot option is previous TW and to boot new one I have to manually select it from the list.

I was able to boot new TW, go to YaST->Loader, on "Loader settings" tab there I see several boot options:
Code:
- openSUSE Tumbleweed                                                                       // new TW, I suppose
- openSUSE Tumbleweed, with Linux <kernel version>
- openSUSE Tumbleweed (on /dev/sda3)                                                  // previous TW
- openSUSE Tumbleweed, with Linux <kernel version> (on /dev/sda3)         // previous TW
…
- openSUSE Tumbleweed, with Linux <kernel version> (on /dev/sda3)         // previous TW
Then I press OK, and after some time YaST->Loader window silently closes, but after reboot I see boot options are like:
Code:
- openSUSE Tumbleweed                                                                      // this one boots old TW from HDD
- openSUSE Tumbleweed, with Linux <kernel version>                             // kernel from old TW         
- openSUSE Tumbleweed (on /dev/sdb2)                                                 // this one boots new TW from SSD
- openSUSE Tumbleweed, with Linux <kernel version> (on /dev/sdb2)        // kernel from new TW
…
Looks like loader from old TW is getting control. Inside BIOS setup, on "Boot sequence" page there is only one record "opensuse-secureboot".

In my system /dev/sda3 is root partition of prev TW on HDD and /dev/sdb2 is root partition of new TW on SSD.
sda1 and sdb1 are /boot/efi with vfat, in order for old and new systems.

My language isn't english, so menu and window titles are might be isn't 100% accurate, sorry for this.

So what should I try that new TW was be able to write his own loader into EFI? May enabled secure-boot prevents this?