Bug 1035808

Summary: RHEL-7 kickstart installation under qemu-kvm fails opening X-Display
Product: Red Hat Enterprise Linux 7 Reporter: Heinz Mauelshagen <heinzm>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Release Test Team <release-test-team>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.0CC: heinzm, Karl.Redgate
Target Milestone: rcKeywords: Reopened
Target Release: ---Flags: heinzm: needinfo-
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1479876 (view as bug list) Environment:
Last Closed: 2014-01-24 21:29:22 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:
Bug Depends On:    
Bug Blocks: 1479876    
Attachments:
Description Flags
RHEL-7-beta kickstart failing none

Description Heinz Mauelshagen 2013-11-28 14:22:42 UTC
Description of problem:

Kickstart installation of RHEL-7.0-20131117.n.0 in a qemu-kvm VM fails with
"** (anaconda:1224): WARNING **: could not open X-Display **"


Version-Release number of selected component (if applicable):
Fedora-19 host
anaconda 19.31.36-1
qemu-kvm-1.4.2-12.fc19

How reproducible:

Run kickstart installation

Steps to Reproduce:
1.
2.
3.

Actual results:

Fails with aforementioned error trying to open X-Display, even thought kickstart installation restricts to text mode.

Expected results:

Kickstart intsllation succeeds.

Additional info:

Comment 2 Heinz Mauelshagen 2013-11-29 12:21:06 UTC
Occured with RHEL-7.0-20131125.n.0

Comment 3 David Cantrell 2013-12-12 18:56:15 UTC
Unable to reproduce the problem using RHEL-7.0-20131127.1.

Comment 4 Heinz Mauelshagen 2013-12-12 23:10:09 UTC
(In reply to David Cantrell from comment #3)
> Unable to reproduce the problem using RHEL-7.0-20131127.1.

David,

I can reproduce this with every RHEL-7 nightly newer than 
RHEL-7-20130920.n.0, which still WFM.

Even RHEL-7-beta does not WFM.

Comment 5 Heinz Mauelshagen 2013-12-12 23:12:13 UTC
Created attachment 836073 [details]
RHEL-7-beta kickstart failing

RHEL-7-beta kickstart file which fails for me.

Comment 6 David Cantrell 2014-01-15 19:23:14 UTC
Please attach /tmp/anaconda.log, /tmp/syslog, and /tmp/X.log from the installation environment.

Comment 7 David Cantrell 2014-01-24 21:29:22 UTC
No logs provided, closing the bug.  If you can provide the information requested in comment #6, feel free to reopen the bug.

Comment 8 Karl.Redgate 2014-02-14 12:23:01 UTC
I am seeing this also.  I am trying to gather logs

Comment 9 Karl.Redgate 2014-02-14 12:29:20 UTC
In my case this is not under KVM, but on a Dell XE2 performing a PXE boot with a kickstart that is trying to do a text mode install.

install
url --url=http://yumhost/distro/rhel/7.0b/x86_64/os
text
skipx
lang en_US.UTF-8
keyboard us
reboot
authconfig --enablemd5 --enableshadow
firewall --disabled
selinux --disabled
bootloader --location=mbr
timezone --utc US/Eastern
network --device=eth0 --bootproto=dhcp --hostname=euler
zerombr
clearpart --all --initlabel
partition /boot --size 128
partition pv.00 --size 1 --grow
volgroup VolumeGroup00 pv.00
logvol / --vgname VolumeGroup00 --size 1 --name=rootlv --grow
%packages
....

Comment 10 Karl.Redgate 2014-02-14 12:41:01 UTC
Looks like the X error is a red herring.  Removing 'text' and 'skipx' and the X message goes away ... however the real anaconda stack trace shows:

...pyanaconda/nm.py, line 200, in nm_device_property
    raise UnknownDeviceError(name, e)
...nm.py, line 274, in nm_device_hwaddress
...network.py, line 515, in add_connection_for_ksdata

This seems like maybe my network line is wrong ... I will test

Comment 11 Karl.Redgate 2014-02-14 12:44:22 UTC
Yes, that was the problem.  The eth0 device is now em1 due to the biosdevname change.  It is past that error now.

Comment 12 Karl.Redgate 2014-02-14 12:47:25 UTC
It looks like my problem here is really a dup of:
https://bugzilla.redhat.com/show_bug.cgi?id=1046307