Strange behaviour with confirm=false

Hello

I've been using autoyast since openSUSE 10.2 and it's a great tool. Thanks to every single 
developer who contributed to it.

While re-testing all the custom control files we use at the lab with Leap 42.3 release I 
have noticed a strange behaviour with the option 'confirm' that controls unattended 
installation.
Here's my scenario : GPT partition table with bios boot (not efi), custom partitioning but 
nothing silly, then various options. Whatever I add to the control file the installation 
process works flawlessly until I finish testing it. Then I turn it to unattended with the 
following directive :

<confirm config:type="boolean">
   false
</confirm>


The installation with full control file goes well but the system won't reboot (no valid 
boot device). After a bit of search I noticed that it is related to the pmbr_boot flag on 
the disk not being set. Adding it manually with parted solves the problem so as a 
workaround I added a very simple chroot-script to make it.

Since I thought I had probably messed up something I did a lot of testing to reproduce it 
(even with minimal control file) and figured that the confirm option is the issue. I can't 
figure how it would affect the bootlader part of the process after package installation 
but it does. Anyone have any idea or should I simply fill a bug report ?

Thanks in advance

Regards
L.
-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]