Description of problem: Anaconda did not read Kickstart file via network inst.ks=(ftp|http) Version-Release number of selected component (if applicable): FC23 How reproducible: always Steps to Reproduce: Use PXE boot for installation and eg. a RedHat tftpd server with this configuration: label fc23test kernel FC23/x86_64/vmlinuz append inst.selinux=0 selinux=0 initrd=FC23/x86_64/initrd.img inst.stage2=ftp://rpm/fedora/linux/releases/23/Server/x86_64/os inst.repo=ftp://rpm/fedora/linux/releases/23/Everything/x86_64/os noipv6 inst.ks=ftp://rpm/auto_inst/fedora-23-test.x86_64.cfg Actual results: Kickstart file is loaded from the ftp server (seen in the ftpd log) but not read by Anaconda. You get the message: Kickstart file not found" Additional info: Fix: Do not use this UNUSEABLE anacoda version, use anaconda from FC21 for a 23 installation: label fc23test kernel FC21/x86_64/vmlinuz append inst.selinux=0 selinux=0 initrd=FC21/x86_64/initrd.img inst.stage2=ftp://rpm/fedora/linux/releases/21/Server/x86_64/os inst.repo=ftp://rpm/fedora/linux/releases/23/Everything/x86_64/os noipv6 inst.ks=ftp://rpm/auto_inst/fedora-23-test.x86_64.cfg
Can you attach the kickstart file you are using, with any passwords and other sensitive data removed? At what point does the file not found message occur? Before the message, do you see something like "anaconda 23.19.10-1 for Fedora 23 started", or something that looks like progress output from fetching the file over the network, or something else?
Created attachment 1115792 [details] fedora-23-min.x86_64.cfg Used Kickstart file
Created attachment 1115793 [details] log of anaconda
Created attachment 1115794 [details] storage log
Created attachment 1115795 [details] prgramm log
ifcfg.log packaging.log and sensitive-info.log are emtpy files. ftp server transfer log: Mon Jan 18 10:51:25 2016 0 134.76.88.196 1131 /mnt/theorie/rpm/fedora/linux/releases/23/Server/x86_64/os/.treeinfo b _ o a ftp ftp 0 * c Mon Jan 18 10:51:29 2016 3 134.76.88.196 346673152 /mnt/theorie/rpm/fedora/linux/releases/23/Server/x86_64/os/images/install.img b _ o a ftp ftp 0 * c Mon Jan 18 10:51:30 2016 0 134.76.88.196 3090 /mnt/theorie/rpm/auto_inst/fedora-23-min.x86_64.cfg b _ o a ftp ftp 0 * c
After digging arround I found this in the journal: File "/usr/lib/python3.4/site-packages/pykickstart/parser.py", line 124, in preprocessKickstart contents = load_to_str(f) File "/usr/lib/python3.4/site-packages/pykickstart/load.py", line 44, in load_to_str return _load_file(location) File "/usr/lib/python3.4/site-packages/pykickstart/load.py", line 93, in _load contents = fh.read() File "/usr/lib64/python3.4/encodings/ascii.py", line 26, in decode return codecs.ascii_decode(input, self.errors)[0] UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2410: ordinal not in range(128) This is related to a comment in the Kickstart file: # ldap Backend für sssd So, utf8 in comments breaks anaconda! I thought the ASCII only time long gone.
*** This bug has been marked as a duplicate of bug 1280448 ***