Description of problem: Fedora-Atomic-dvd-x86_64-Rawhide-20160924.n.0.iso anaconda-26.4-1.fc26 default installation, crashes during "configuring installed system" Version-Release number of selected component: anaconda-26.4-1 The following was filed automatically by anaconda: anaconda 26.4-1 exception report Traceback (most recent call first): File "/usr/lib64/python3.5/site-packages/pyanaconda/iutil.py", line 787, in enable_service raise ValueError("Error enabling service %s: %s" % (service, ret)) File "/usr/lib64/python3.5/site-packages/pyanaconda/kickstart.py", line 1697, in execute iutil.enable_service(svc) File "/usr/lib64/python3.5/site-packages/pyanaconda/install.py", line 78, in doConfiguration ksdata.services.execute(storage, ksdata, instClass) 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) ValueError: Error enabling service chronyd: 1 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-Rawhide-x86_64 quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.8.0-0.rc7.git4.1.fc26.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: rawhide Potential duplicate: bug 1331864
Created attachment 1204616 [details] File: anaconda-tb
Created attachment 1204617 [details] File: anaconda.log
Created attachment 1204618 [details] File: environ
Created attachment 1204619 [details] File: lsblk_output
Created attachment 1204620 [details] File: lvm.log
Created attachment 1204621 [details] File: nmcli_dev_list
Created attachment 1204622 [details] File: os_info
Created attachment 1204623 [details] File: program.log
Created attachment 1204624 [details] File: storage.log
Created attachment 1204625 [details] File: syslog
Created attachment 1204626 [details] File: ifcfg.log
*** This bug has been marked as a duplicate of bug 1331864 ***