Bug 1110736

Looks like there is some issue when mounting /boot partition:

2018-10-04 12:58:36 <1> install(3645) [Ruby] modules/RootPart.rb:1220 mounting /dev/system/swapvol to swap
2018-10-04 12:58:36 <1> install(3645) [Ruby] modules/RootPart.rb:1116 mounting UUID="4e3b5902-0bfb-4d0b-aa1a-8b926b135cdb" to /boot
2018-10-04 12:58:36 <3> install(3645) [libstorage] BlkDevice.cc:49 THROW:        device not found, name:UUID="4e3b5902-0bfb-4d0b-aa1a-8b926b135cdb"

can you see in the logs where that partition UUID came from?
because when I boot a rescue system, mount root, dev, sys and proc, then chroot into it and do a "mount -a" all partitions get mounted just fine, so it can't be from /etc/fstab.

hmmm ... that UUID is in fact in /etc/fstab, and it's my /boot partition.

but like I said:

if i do this in a rescue system:

mnt /dev/system/rootvol /mnt
mnt -o bind /dev /mnt/dev
mnt -o bind /sys /mnt/sys
mnt -o bind /proc /mnt/proc
chroot /mnt /bin/bash --login
mount -a

it works just fine and that partition is mounted on /boot as it should.

This issues has been likely already fixed but we cannot update the already released DVD.

However, there are some unofficial ways how to get the latest installer.
Please try the options described at https://bugzilla.suse.com/show_bug.cgi?id=1094749#c21 and let us know if that helps.

interesting. my boot screen on my Leap 15.0 installer DVD looks completely different from what i can see in openQA.

I think i did manage to pass the option at the right spot, it goes where all kernel options go in grub2, right? ... had to edit the boot entry.

...same error. method A did not help. It did seem to apply the newer packages from that repo tho.

Created attachment 785101 [details]
another batch of logfiles, this one WITH the upgraded yast modules

hm. the installer does *not* ask me for confirmation for adding an untrusted repo...

tried it three times. my boot screen does *not* look like the one past the link to openQA, how/where do i add that SELF_UPDATE parameter? I've added it to the linuxefi line when editing the grub entry.

(In reply to Mathias Homann from comment #8)
> hm. the installer does *not* ask me for confirmation for adding an untrusted
> repo...
> 
> tried it three times. my boot screen does *not* look like the one past the
> link to openQA, how/where do i add that SELF_UPDATE parameter? I've added it
> to the linuxefi line when editing the grub entry.

d'oh. yast never asks for network information, how is it supposed to add that repo?

(In reply to Mathias Homann from comment #9)
> (In reply to Mathias Homann from comment #8)
> > hm. the installer does *not* ask me for confirmation for adding an untrusted
> > repo...
> > 
> > tried it three times. my boot screen does *not* look like the one past the
> > link to openQA, how/where do i add that SELF_UPDATE parameter? I've added it
> > to the linuxefi line when editing the grub entry.
> 
> d'oh. yast never asks for network information, how is it supposed to add
> that repo?

turns out that until now the updates were *not* installed. YaST does not want to use wifi at this stage of an installation.

d'oh. cat6 to the rescue. repository was properly added this time, and the crash didn't happen.

it sure helps when you actually watch the screen during this kind of stuff.

ok, the upgraded yast modules from the repository mentioned in https://bugzilla.suse.com/show_bug.cgi?id=1094749#c21 fixed this. Upgrade is progressing normally.

I strongly suggest releasing updated ISO images tho.