(In reply to Josef Reidinger from comment #0)
> Created attachment 840857 [details]
> y2logs
> 
> autoyast profile specify 2 disks out of 5 on system. Storage proposal use
> one of that disks, but reuse swap from not specified disk, which is not
> intended.

It would be nice to have the profile attached too.

> 
> For details see attached yast logs.

See

> 2020-08-20 04:32:25 <1> dhcp67(4181) [Ruby] devices_planner_strategies/ng.rb:219 planned to reuse swap /dev/vdd2

I think that, by default, the manual proposal tries to use an existing swap instead of creating a new one. But I have to check such a behavior. A different matter is if we want AutoYaST to behave like that.

If I recall correctly, the partitioning section was something like this:

<partitioning t="list">
  <drive>
    <initialize t="boolean">true</initialize>
    <device>/dev/vda</device>
  </drive>
  <drive>
    <initialize t="boolean">true</initialize>
    <device>/dev/vdb</device>
  </drive>
</partitioning>

(In reply to Imobach Gonzalez Sosa from comment #2)
> I think that, by default, the manual proposal tries to use an existing swap
> instead of creating a new one. But I have to check such a behavior. A
> different matter is if we want AutoYaST to behave like that.
> 
> If I recall correctly, the partitioning section was something like this:
> 
> <partitioning t="list">
>   <drive>
>     <initialize t="boolean">true</initialize>
>     <device>/dev/vda</device>
>   </drive>
>   <drive>
>     <initialize t="boolean">true</initialize>
>     <device>/dev/vdb</device>
>   </drive>
> </partitioning>

What would occur if multiple drives has SWAP partitions? If there's some kind of sensible criteria, it might be worth retaining, but if it just chooses a partition at seemingly random, then it might be more sensible for it to default to the installation partition.