Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 951632

Summary: Kickstart installation in text-mode doesn't run on s390x
Product: [Fedora] Fedora Reporter: Dan Horák <dan>
Component: anacondaAssignee: Samantha N. Bueno <sbueno>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: g.kaviyarasu, jonathan, jstodola, mkolman, sbueno, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-23 13:48:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 467765, 951094    
Attachments:
Description Flags
anaconda.log
none
ifcfg.log
none
packaging.log
none
program.log
none
storage.log
none
syslog
none
ps auxf none

Description Dan Horák 2013-04-12 16:14:42 UTC 
Description of problem:
Kickstart installation in text-mode on s390x stops right after starting anaconda.

...
[ [32m  OK   [0m] Started System Logging Service.   
anaconda[1066]: Starting installer, one moment... 
anaconda[1066]: anaconda 19.18-1 for Fedora 20130412 (pre-release) started. 
anaconda[1066]: 16:13:50 Not asking for VNC because text mode was explicitly ask
ed for in kickstart 


Nothing else is happening, anaconda uses 100% of CPU.

Version-Release number of selected component (if applicable):
anaconda-19.18-1.fc19

How reproducible:
always

Steps to Reproduce:
1. start text-mode kickstart installation on s390x
  
Actual results:
Installation doesn't proceed

Expected results:
Installation finishes
Comment 1 Dan Horák 2013-04-12 16:15:55 UTC 
Created attachment 734818 [details]
anaconda.log
Comment 2 Dan Horák 2013-04-12 16:16:34 UTC 
Created attachment 734819 [details]
ifcfg.log
Comment 3 Dan Horák 2013-04-12 16:17:37 UTC 
Created attachment 734820 [details]
packaging.log
Comment 4 Dan Horák 2013-04-12 16:17:56 UTC 
Created attachment 734821 [details]
program.log
Comment 5 Dan Horák 2013-04-12 16:18:18 UTC 
Created attachment 734822 [details]
storage.log
Comment 6 Dan Horák 2013-04-12 16:18:36 UTC 
Created attachment 734823 [details]
syslog
Comment 7 Dan Horák 2013-04-12 16:19:02 UTC 
Created attachment 734824 [details]
ps auxf
Comment 8 Dan Horák 2013-04-12 17:05:14 UTC 
after attaching strace

...
access("/tmp/curl_fetch_url0/install.img", R_OK) = -1 ENOENT (No such file or directory)
access("/LiveOS/rootfs.img", R_OK)      = -1 ENOENT (No such file or directory)
access("/overlay", R_OK)                = -1 ENOENT (No such file or directory)
access("/tmp/curl_fetch_url0/install.img", R_OK) = -1 ENOENT (No such file or directory)
access("/LiveOS/rootfs.img", R_OK)      = -1 ENOENT (No such file or directory)
access("/overlay", R_OK)                = -1 ENOENT (No such file or directory)
access("/tmp/curl_fetch_url0/install.img", R_OK) = -1 ENOENT (No such file or directory)
access("/LiveOS/rootfs.img", R_OK)      = -1 ENOENT (No such file or directory)
access("/overlay", R_OK)                = -1 ENOENT (No such file or directory)
access("/tmp/curl_fetch_url0/install.img", R_OK) = -1 ENOENT (No such file or directory)
....
Comment 9 Dan Horák 2013-04-29 10:19:43 UTC 
I don't see this issue with anaconda 19.21 (with http://fedoraproject.org/wiki/Architectures/s390x/19#issues_found_in_F-19_post-Alpha_20130424) anymore