Comment # 38 on bug 949796 from Bruno Pesavento

(In reply to Josef Reidinger from comment #33)
> (In reply to Hannes Reinecke from comment #30)
> > But still, you might want to fixup yast2-bootloader, too.
> > 
> > yast2 crashing is always horrible, for whatever reason.
> > Blaming that on the underlying programs is not a good design principle.
> > 
> > Josef, have you fixed up yast2?
> 
> What can be changed is to modify storage to not use wwn as udev device. But
> how do you expect I can fix yast2-bootloader? grub2 have specified that it
> is booting from /dev/disk/by-id/wwn* so yast2-bootloader report problem, as
> it do not know what it is.
>...
This is not entirely true, at least in my setup.
My current GRUB2 setup references UUIDs throughout, local disks only, no
attempt at even looking for WWNs.
I didn't even "know" about WWNs until this bug surfaced.
>From what I see here, Yast warns and exits just looking at /dev/disk/by-id and
doesn't even get to GRUB files.
If I manually change the GRUB config and rebuild GRUB, everything works.
The system has been "zypper dup"-ed several times since the bug appeared, GRUB
menu updated, newly installed kernels booted without problems.
Maybe just deferring the WWN check until an actual attempt at using network
disks, where hopefully needed WWNs are in place, could be a safer choice.
Just an user's standpoint...