User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
Firefox/52.0
Build Identifier: 

Running a Dell XPS 15 9550 with a 512 GB NVMe PCIe drive. Partitions are setup
with an EFI partition, then Windows 10, then about a 300 GB gap (for
Tumbleweed), then Windows recovery partitions. I booted the Live USB in UEFI
mode with legacy booting entirely disabled in my BIOS/UEFI. I set up custom
partitioning to change the increase the size of root and decrease the size of
home, both partitions were set to btrfs. The installer found my existing EFI
partition and set it to mount at /boot/efi as I would expect. On the next page,
the bootloader was set to Grub2 rather than Grub2 for EFI. I didn't notice this
in my first install of Tumbleweed, so Grub installed in Legacy mode and made my
drive completely unbootable in UEFI mode. I had to restore the drive entirely
using a Windows 10 recovery disk to fix the damage from the installer. In my
case this didn't really matter, but the existing Windows partition was
essentially lost entirely. The same Grub default occurred on my second install,
but I changed it to Grub2 for EFI this time and the install worked correctly.

Reproducible: Always

Steps to Reproduce:
1.Have an NVMe PCIe drive with an existing UEFI Windows 10 partition
2.Disable Legacy Boot in the UEFI/BIOS
3.Boot into Tumbleweed UEFI Live USB
4.Run installer,set both root and home partitions to btrfs
5.Don't set /boot/efi mount point since it was already autodetected
6.Go to final page of the installer before confirming the install
Actual Results:  
Grub2 (non EFI) was selected as the default bootloader, which is apparently a
dangerous default for an existing UEFI system based on my results (major system
breakage, had to reformat entirely)

Expected Results:  
Grub2 for EFI should be the default since my existing system is UEFI, the Live
USB is UEFI, and my drive is GPT formatted with an EFI boot partition that the
installer correctly found. 

After the installer ran, my NVMe drive no longer appeared in the UEFI boot
options at all. Any boot entry created through efibootmgr that pointed to the
drive would simply not show up in the boot menu. Boot entries that pointed to
the drive as if it was an MBR disk would show up in the boot menu but would
fail to boot. The NVMe drive still showed up as a legacy boot option and would
boot successfully into OpenSUSE. When booting in legacy mode, Grub would detect
my existing Windows bootloader but would fail to boot it with "invalid
signature." Let me know if you need any other information, hopefully this was
helpful.