Bug 952348

Summary: kickstart fails with stack trace
Product: [Fedora] Fedora Reporter: Dean Hunter <deanhunter>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 19CC: anaconda-maint-list, bcl, g.kaviyarasu, jonathan, mkolman, sbueno, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-15 19:22:12 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:
Attachments:
Description Flags
Here is a listing of /tmp
none
Here is a screen shot of the end of the stack trace.
none
Here is a screen shot of the beginning of the stack trace.
none
Here is a screen shot of the beginning of the SELinux alerts. none

Description Dean Hunter 2013-04-15 18:29:23 UTC
Description of problem:
I am trying to do an Anaconda Kickstart installation of Fedora-19-Alpha-TC6. I did a manual install first and I am using the anaconda-ks.cfg after removing the comments and alphabetizing the statements. Anaconda starts but fails quickly with a stack trace. The beginning of the trace scrolls off the display and I am not able to cut and paste the display. I can switch to tty2, but there is no information about the stack trace in any of the log files.


Version-Release number of selected component (if applicable):
Fedora 19 Alpha TC6


How reproducible:
Consistent


Steps to Reproduce:
1. wget --output-document=/home/qemu/ISO/Fedora-19-x86_64.iso \
    https://dl.fedoraproject.org/pub/alt/stage/19-Alpha-TC6/Fedora/x86_64/iso/Fedora-19-Alpha-TC6-x86_64-DVD.iso \

2. cat >/tmp/Fedora19/step2 <<EOF
auth       --enableshadow --passalgo=sha512
autopart   --type=lvm
bootloader --location=mbr --boot-drive=vda
cdrom
clearpart  --none --initlabel --drives=vda
firstboot  --enable
ignoredisk --only-use=vda
keyboard   --vckeymap=us --xlayouts='us'
lang         en_US.UTF-8
network    --bootproto=dhcp --device=eth0 --ipv6=auto --nameserver=192.168.1.11 --activate
network    --hostname=fedora19.hunter.org
rootpw     --iscrypted \$6\$cIJfp.FzNHAoErha\$oju1/jJuF.epNFYojgYTsyyq2ygZwRrY5gD5vgj5m09G7SjXLD/kAuLQNDzcZ467cYMiZEljVpltguxJQnQ6y1
services   --enabled="chronyd"
timezone     America/Chicago --isUtc
user       --groups=wheel --name=local --password=\$6\$6YuUd3dm5L5ALg25\$I6Tg.twaZxA/NePE/yNTmY3HoUNt5Za5vDQMjCGB8Fp22ANG0y0usmAn/f14xGwDZ1QcSVWTWqDjl7kDkSZAO/ --iscrypted --gecos="Local Administrator"
xconfig    --startxonboot

%packages
@base-x
@core
@dial-up
@firefox
@fonts
@gnome-desktop
@hardware-support
@input-methods
@multimedia
@printing
@standard
chrony
%end
EOF

3. virt-install \
    --autostart \
    --cpu host \
    --disk vol=Guests/Fedora19 \
    --extra-args "inst.ks=file:/step2" \
    --graphics spice \
    --initrd-inject /tmp/Fedora19/step2 \
    --location /home/qemu/ISO/Fedora-19-x86_64.iso \
    --name Fedora19 \
    --network network=Host \
    --os-type "linux" \
    --os-variant "fedora18" \
    --ram 2048 \
    --vcpus 2 \
    --video qxl

  
Actual results:
Stack trace in /usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py


Expected results:
Successful installation


Additional info:

Comment 1 Chris Lumens 2013-04-15 18:35:27 UTC
Are you not getting a /tmp/anaconda-tb-* file?  If you are, please attach that.  if not, you can scroll back on window #1 the way you can elsewhere using tmux (ctrl-b [ and then use page up/down) and attach a picture.

Comment 2 Dean Hunter 2013-04-15 18:50:55 UTC
Created attachment 736024 [details]
Here is a listing of /tmp

Comment 3 Dean Hunter 2013-04-15 18:53:23 UTC
Created attachment 736025 [details]
Here is a screen shot of the end of the stack trace.

Comment 4 Dean Hunter 2013-04-15 18:56:39 UTC
Created attachment 736026 [details]
Here is a screen shot of the beginning of the stack trace.

Comment 5 Dean Hunter 2013-04-15 19:01:03 UTC
This is the first I have heard of tmux. I learned something new today. Thank you.

Did I get you what you need?

Comment 6 Dean Hunter 2013-04-15 19:09:10 UTC
I should also mention that while checking /tmp/syslog I found a large number of SELinux alerts (avc).

Comment 7 Dean Hunter 2013-04-15 19:09:58 UTC
Created attachment 736027 [details]
Here is a screen shot of the beginning of the SELinux alerts.

Comment 8 David Lehman 2013-04-15 19:22:12 UTC

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