Bug 1134796

Summary: Expert Partitioner during installation does not work.
Product: [openSUSE] openSUSE Tumbleweed Reporter: Damian Höster <damian.hoester>
Component: YaST2Assignee: E-mail List <yast2-maintainers>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Major    
Priority: P5 - None CC: damian.hoester, vinz
Version: Current   
Target Milestone: ---   
Hardware: x86-64   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: y2logs, created after starting the Expert Partitioner failed.
This happens when I want to start the Expert Partitioner
y2logs after expert partitioner failed

Description Damian Höster 2019-05-11 15:55:45 UTC
Created attachment 804803 [details]
y2logs, created after starting the Expert Partitioner failed.

The Expert Partitioner during installationdoes not work. It even failed when there was only one SATA drive with no partitions on it in the system.
The Guided Setup worked fine.
Comment 1 Martin Vidner 2019-05-13 08:30:21 UTC
Thank you for the report!

"does not work" and "failed" is a broad concept.
Do you click a button and nothing happens?
Does YaST stop responding?
Does it crash?
Comment 2 Damian Höster 2019-05-13 10:22:11 UTC
Created attachment 804866 [details]
This happens when I want to start the Expert Partitioner

This happens when I want to start the Expert Partitioner
Comment 3 Vinzenz Vietzke 2019-05-15 20:28:53 UTC
Created attachment 805188 [details]
y2logs after expert partitioner failed

I can confirm the issue and so did someone on German mailinglist. The error message is:
===
Internal error. Please report a bug report with logs.
Run save_y2logs to get complete logs.

Caller:
/mounts/mp_0001/usr/share/YaST2/lib/y2partitioner/widgets/blk_devices_table.rb:297:in
`format'

Details: key{Ds_Typ} not found
Did you mean? :fs_type

Start the Ruby debugger now and debug the issue? (Experts only!)
===
y2logs are attached.
Comment 4 Arvin Schnell 2019-05-15 20:58:59 UTC
Duplicate of bug #1134685.

*** This bug has been marked as a duplicate of bug 1134685 ***