Description of problem: Run a default install with Fedora-Atomic-dvd-x86_64-25-20160912.n.0.iso . It crashes at post-install stage. This is fully and trivially reproducible. Version-Release number of selected component: anaconda-25.20.1-1 The following was filed automatically by anaconda: anaconda 25.20.1-1 exception report Traceback (most recent call first): File "/usr/lib64/python3.5/site-packages/pyanaconda/screen_access.py", line 82, in write_out_config_file with open(config_path, "wt") as f: File "/usr/lib64/python3.5/site-packages/pyanaconda/install.py", line 134, in doConfiguration screen_access.sam.write_out_config_file() File "/usr/lib64/python3.5/threading.py", line 862, in run self._target(*self._args, **self._kwargs) File "/usr/lib64/python3.5/site-packages/pyanaconda/threads.py", line 251, in run threading.Thread.run(self, *args, **kwargs) FileNotFoundError: [Errno 2] No such file or directory: '/mnt/sysimage/etc/sysconfig/anaconda' Additional info: addons: com_redhat_docker, com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-25-x86_64 quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.8.0-0.rc4.git0.1.fc25.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 25
Created attachment 1200573 [details] File: anaconda-tb
Created attachment 1200574 [details] File: anaconda.log
Created attachment 1200575 [details] File: environ
Created attachment 1200576 [details] File: lsblk_output
Created attachment 1200577 [details] File: lvm.log
Created attachment 1200578 [details] File: nmcli_dev_list
Created attachment 1200579 [details] File: os_info
Created attachment 1200580 [details] File: storage.log
Created attachment 1200581 [details] File: syslog
Created attachment 1200582 [details] File: ifcfg.log
Created attachment 1200583 [details] File: program.log
This would probably affect Rawhide too, only Rawhide is still running into https://bugzilla.redhat.com/show_bug.cgi?id=1331864 instead.
Similar problem has been detected: This is an Fedora-Atomic-dvd-x86_64-25-20160912.n.0.iso installation, using the Btrfs partition scheme in manual partitioning; that fails on bug 1289752 but lets me continue anyway, at which point during post-install scripts I get a crash. addons: com_redhat_docker, com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-25-x86_64 elevator=noop hashmarkername: anaconda kernel: 4.8.0-0.rc4.git0.1.fc25.x86_64 package: anaconda-25.20.1-1 packaging.log: product: Fedora reason: FileNotFoundError: [Errno 2] No such file or directory: '/mnt/sysimage/etc/sysconfig/anaconda' release: Cannot get release name. version: 25
Yeah it works for me with a default autopart installation also. Fedora-Atomic-dvd-x86_64-24-20160914.0.iso installs OK.
openQA does a default partitioning install. It hits this bug. 24 is different from 25.
Yeah sorry Fedora-Atomic-dvd-x86_64-25-20160912.n.0.iso fails for me as described in this bug no matter what the layout is, including default.
This is https://github.com/rhinstaller/anaconda/pull/790
Similar problem has been detected: Installation to a single partition formatted XFS in a VM pointed at an LV. 1. 500G virtual LV 2. boot Fedora-Atomic-dvd-x86_64-25-20160912.n.0.iso 3. custom partition, create a single XFS volume (no swap, no lvm, nothing else) 4. install crash addons: com_redhat_docker, com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-25-x86_64 quiet hashmarkername: anaconda kernel: 4.8.0-0.rc4.git0.1.fc25.x86_64 package: anaconda-25.20.1-1 packaging.log: product: Fedora reason: FileNotFoundError: [Errno 2] No such file or directory: '/mnt/sysimage/etc/sysconfig/anaconda' release: Cannot get release name. version: 25
Oh cute I've already been here before!
Should be fixed by this: https://github.com/rhinstaller/anaconda/pull/872 Testing welcome! :)
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.