Turns out the root of the error was an uncaught exception at the GuidedProposal caused because YaST was trying to adjust the sizes of the root device to fulfill the Btrfs-related settings... but such a device was a disk instead of an LV or partition.
Solution
Added the same guard we have in other parts of DevicesPlanner (eg. adjust_sizes).
Testing
Added a new unit test
Tested manually with Agama. It solves the reported bug.
coverage: 97.804%. remained the same
when pulling ace78c6dc83a0d325ede9d81babc2cc05bbb7930 on ancorgs:fix-agama-btrfs-disk
into 034d1fb3d1a57ff36f8676fa7e1d44af54c19ae9 on yast:master.
coverage: 97.804%. remained the same
when pulling f90b6d57fe621a7ef5a546bfc85b1ca2938477e6 on ancorgs:fix-agama-btrfs-disk
into 034d1fb3d1a57ff36f8676fa7e1d44af54c19ae9 on yast:master.
coverage: 97.804%. remained the same
when pulling 60a876a8b4419b1222699bcabb10f28d8acc0598 on ancorgs:fix-agama-btrfs-disk
into 034d1fb3d1a57ff36f8676fa7e1d44af54c19ae9 on yast:master.
Problem
This bug at Agama was reported https://github.com/openSUSE/agama/issues/1339
Turns out the root of the error was an uncaught exception at the GuidedProposal caused because YaST was trying to adjust the sizes of the root device to fulfill the Btrfs-related settings... but such a device was a disk instead of an LV or partition.
Solution
Added the same guard we have in other parts of
DevicesPlanner
(eg.adjust_sizes
).Testing