Comment # 5 on bug 1208258 from Stefan Hundhammer

That other message is probably harmless:


22023-02-12 17:08:06 <1> install(3533) [Ruby]
  bin/y2start(<main>):22
  y2base called with
  ["installation", "--arg", "initial", "qt", "--noborder",
  "--auto-fonts", "--fullscreen"]

...
...

023-02-12 12:22:02 <3> ip-10-0-2-15(3533) [bash]
  ShellCommand.cc(shellcommand):78
  /bin/cp: cannot stat '/mnt/boot/vmlinuz':
  No such file or directory

2023-02-12 12:22:02 <1> ip-10-0-2-15(3533) [Ruby]
  bootloader/kexec.rb(copy_kernel):110
  Command for copy: /bin/cp -L
  /mnt/boot/vmlinuz /mnt/boot/initrd /var/lib/YaST2
  and result
  {"exit"=>1, "stderr"=>
  "/bin/cp: cannot stat '/mnt/boot/vmlinuz':
  No such file or directory\n",
  "stdout"=>""}

2023-02-12 12:22:02 <3> ip-10-0-2-15(3533) [Ruby]
  bootloader/kexec.rb(copy_kernel):112
  Copy kernel and initrd failed, output:
  {"exit"=>1, "stderr"=>
  "/bin/cp: cannot stat '/mnt/boot/vmlinuz':
  No such file or directory\n",
  "stdout"=>""}


/boot/vmlinuz (or like here in the inst-sys, /mnt/boot/vmlinuz) is normally a
symlink to the current default kernel. It looks like at that point that link
does not (yet) exist. But a kernel with the full name obviously exists because
the system booted successfully.

Why we are trying to copy (as a symlink (-L), if possible) the current kernel
and the initrd to /var/lib/YaST2 is not clear to me; possibly to use "kexec"
instead of a real boot.

But anyway, this is nothing to worry about AFAICS.