Bug 1221087

Summary: [Agama live-cd] Partitioning proposal offers to resize partition without knowing enough info about it
Product: [openSUSE] openSUSE Tumbleweed Reporter: Lukas Ocilka <locilka>
Component: InstallationAssignee: YaST Team <yast-internal>
Status: CONFIRMED --- QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None    
Version: Current   
Target Milestone: ---   
Hardware: Other   
OS: Other   
URL: https://trello.com/c/7tDOQ06Z
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Storage details
cfdisk sdb2
cfdisk sdb4
Logs from Agama

Description Lukas Ocilka 2024-03-06 16:43:25 UTC
Created attachment 873269 [details]
Storage details

While testing the current (2024-03-06) partitioning proposal in Agama, I found out that it lets me to resize partitions without knowing enough info about them.

1. One was 1/2 of RAID 0 - A "Linux" partition (sdb2)
   In TW this leads at least into getting a warning that I may (and probably
   will loose some data)
   The other 1/2 of that RAID is missing in that system, that's why the RAID is 
   not assembled

2. Another was a LUKS1-encrypted partition where I did not provide a pass for 
   decryption (sdb4)
   Here it does not complain and I can simply shrink it to an unreasonable 
   minimum, yes - there are data, but they are of course ignored

How to reproduce

- Have some LUKS1 and/or part of RAID ;) on your disk(s)
- Start Agama live
- When it asks for the encryption password for the LUKS1 device(s), don't 
  provide them and just [Skip]
- At the proposal, go to the Storage
- Select the Installation Device what contains those partitions
- In Find Space, choose "Shrink existing partitions"
- Check the Used Devices and Planned Actions

See

- sdb2 (1/2 RAID): content - Not identified, size X GB, shrinkable by X GB
- sdb4 (LUKS1): content - Not identified, size Y GB, shrinkable by Y GB
- Planned actions: Shrink ancryption layer from 0 B to XX GB <- bug? Maybe 
  because it knows nothing about the FS?
Comment 1 Lukas Ocilka 2024-03-06 16:48:38 UTC
Created attachment 873270 [details]
cfdisk sdb2
Comment 2 Lukas Ocilka 2024-03-06 16:48:58 UTC
Created attachment 873271 [details]
cfdisk sdb4
Comment 3 Lukas Ocilka 2024-03-06 16:55:26 UTC
Created attachment 873272 [details]
Logs from Agama

And yes, I "DO" have a weird setup of disks. All three of them contain some older systems or parts of them. It's for the testing of the behavior.