http://bugzilla.suse.com/show_bug.cgi?id=1155545 http://bugzilla.suse.com/show_bug.cgi?id=1155545#c22 --- Comment #22 from Fabian Vogt <fvogt@suse.com> --- Shortly back to the original topic: I debugged this a bit and found the culprit. To make the proposal, the bootloader module ends up comparing BootloaderFactory.current with the bootloader type of the target system: https://github.com/yast/yast-bootloader/blob/8630995161b572eac13326e38400438... current is defined as (system || proposed), which means that if there is a system bootloader detected, it tries to migrate to that one instead of performing an upgrade. In the live environment, /etc/sysconfig/bootloader has LOADER_TYPE set to grub2-efi. So this is effectively just another manifestation of bnc#874646: https://github.com/yast/yast-bootloader/blob/8630995161b572eac13326e38400438... As LOADER_TYPE on the live medium is meaningless anyway, I'll try to just remove that line. Then system evaluates to nil and current == proposed, which works as expected: https://openqa.opensuse.org/tests/1104031 I did notice that upgrade installation fails in the bootloader proposal (also tested the standard NET .iso) if the driver for the /boot drive changed. In the first test I accidentally used the QEMU default of ata_piix instead of virtio-blk used by openQA, so YaST aborted the upgrade with "Unknown udev device '/dev/disk/by-path/pci-0000:00:08.0'". Does that count as a bug? If so, I'll file a report with logs. -- You are receiving this mail because: You are on the CC list for the bug.