Bug 1094837

Summary: Calling the Yast module "inst_update_partition" has failed
Product: [openSUSE] openSUSE Distribution Reporter: Peter Stolz <stolz>
Component: InstallationAssignee: E-mail List <yast2-maintainers>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Major    
Priority: P5 - None CC: mvidner, stolz
Version: Leap 15.0   
Target Milestone: ---   
Hardware: x86-64   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: YAST logs

Description Peter Stolz 2018-05-28 08:54:35 UTC 
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
Build Identifier: 

I tried to upgrade my Leap 42.3 to Leap 15 with DVD. The installation fails with the error "Calling the Yast module "inst_update_partition" has failed"

Reproducible: Always

Steps to Reproduce:
1. Boot system with Leap 15 installation DVD
2. Choice upgrade the system
3. Choose the suggested root-Partition of Leap 42.3 to upgrade
Actual Results:  
1. Boot system with Leap 15 installation DVD
2. Choice upgrade the system
3. Choose the suggested root-Partition of Leap 42.3 to upgrade

Expected Results:  
Installation fails with the following error message:
"Calling the Yast module "inst_update_partition" has failed"

Upgrade my Leap 42.3 to Leap 15.0
Comment 1 Martin Vidner 2018-05-28 12:46:50 UTC 
Thanks for the report!

Please attach the YaST logs: https://en.opensuse.org/openSUSE:Report_a_YaST_bug

(Note to self: possible duplicate, as it fails in the same file: https://bugzilla.suse.com/show_bug.cgi?id=1094749 )
Comment 2 Peter Stolz 2018-05-28 13:47:28 UTC 
Created attachment 771564 [details]
YAST logs
Comment 3 Peter Stolz 2018-05-28 14:23:49 UTC 
The bug is duplicate with bug 1094749. 
In /etc/fstab I commented out a line to an external Hard-disk-drive which was not connected. This solved the problem.

Thanks!
Comment 4 Peter Stolz 2018-05-28 14:24:42 UTC 
Similiar to bug 1094749

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