Bug 1175535

Summary: Storage proposal reuse swap from disk not specified in AY profile
Product: [openSUSE] openSUSE Tumbleweed Reporter: Josef Reidinger <jreidinger>
Component: AutoYaSTAssignee: YaST Team <yast-internal>
Status: CONFIRMED --- QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: dgonzalez, igonzalezsosa
Version: Current   
Target Milestone: ---   
Hardware: Other   
OS: Other   
URL: https://trello.com/c/reghQm5A
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: y2logs

Description Josef Reidinger 2020-08-20 11:51:42 UTC
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.

For details see attached yast logs.
Comment 1 David Diaz 2020-08-20 14:00:25 UTC
(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
Comment 2 Imobach Gonzalez Sosa 2020-08-21 07:07:56 UTC
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>