Description of problem: The user command from a ks.cfg file used for installation is not written to the resulting anaconda-ks.cfg Version-Release number of selected component (if applicable): anaconda-11.1.2.172-1 How reproducible: Always Steps to Reproduce: 1. Install with a ks.cfg file specifying the user command Actual results: The line containing user command is not present in anaconda-ks.cfg post install Expected results: The user line is present in anaconda-ks.cfg. If --password is specified in plain text then it should appear encrypted and --encrypted will be appended to the line. Additional info: ks.cfg for install: lang en_US.UTF-8 key --skip keyboard us network --device eth0 --bootproto dhcp --hostname ks-user-bug rootpw redhat authconfig --enableshadow --enablemd5 #firewall --disabled #selinux --disabled timezone --utc Europe/London clearpart --all autopart bootloader --location=mbr skipx reboot user --name=redhat %packages @base
I think the best fix for this bug would be to simply copy the input kickstart file to /root/anaconda-ks.cfg instead of writing out yet another file that's likely going to have some very subtle differences from the input. That way we'd never have to deal with this sort of problem again. I could swear I've done this in the past, but I was unable to find any commits that do it.
What about %pre and %post scripts? I've been told in the past that they are not written to the resulting anaconda-ks.cfg for security reasons. Probably you'll have to skip the scripts and leave everything else as is.
I haven't heard that before, but I can believe it. It would make doing what I suggested much more complicated.
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.