When exporting the AutoYaST profile (ie. when cloning the system), LVM thin volumes were ignored.
According to AutoYaST documentation, the thin pool and all its thin volumes must be included as <partition> elements within the <drive> that represents the LVM volume group.
In the devicegraph, the thin pool and its thin volumes are not represented at the same hierarchy level. The volumes are nested into the pool. That was overlooked when implementing the code to clone the system.
Solution
Ensure all logical volumes are taken into consideration, despite the nesting. With that, the exported profile includes the thin pool as well as all its thin volumes.
Testing
Added a regression unit test.
Fix verified by the bug reporter in the real affected system.
Coverage: 97.755%. Remained the same when pulling 285387cad3cfa58b3d5cf81616edbe3945d104da on ancorgs:export_thin into 7d67d4a2ad22a0b2db2c49482d7bbdd74d7240aa on yast:master.
Problem
Fix for bsc#1209725
When exporting the AutoYaST profile (ie. when cloning the system), LVM thin volumes were ignored.
According to AutoYaST documentation, the thin pool and all its thin volumes must be included as
<partition>
elements within the<drive>
that represents the LVM volume group.In the devicegraph, the thin pool and its thin volumes are not represented at the same hierarchy level. The volumes are nested into the pool. That was overlooked when implementing the code to clone the system.
Solution
Ensure all logical volumes are taken into consideration, despite the nesting. With that, the exported profile includes the thin pool as well as all its thin volumes.
Testing