Description of problem: This is probably a direct result from bug #1276372. After anaconda finished installing a set of 250 packages (I guess minimal package set) it tried to configure the root account for which I have not provided a password because there's no way to do so. On the progress screen there are no buttons to configure the root password or additinal users. Version-Release number of selected component: anaconda-24.5-0.1.20151029122830 The following was filed automatically by anaconda: anaconda 24.5-0.1.20151029122830 exception report Traceback (most recent call first): File "/home/atodorov/anaconda/pyanaconda/users.py", line 409, in setUserPassword raise OSError("Unable to set password for new user: status=%s" % proc.returncode) File "/home/atodorov/anaconda/pyanaconda/users.py", line 417, in setRootPassword return self.setUserPassword("root", password, isCrypted, isLocked, algo, root) File "/home/atodorov/anaconda/pyanaconda/kickstart.py", line 1618, in execute users.setRootPassword(self.password, self.isCrypted, self.lock, algo, iutil.getSysroot()) File "/home/atodorov/anaconda/pyanaconda/install.py", line 94, in doConfiguration ksdata.rootpw.execute(storage, ksdata, instClass, u) File "/usr/lib64/python3.4/threading.py", line 868, in run self._target(*self._args, **self._kwargs) File "/home/atodorov/anaconda/pyanaconda/threads.py", line 253, in run threading.Thread.run(self, *args, **kwargs) OSError: Unable to set password for new user: status=3 Additional info: addons: org_fedora_realm cmdline: /usr/bin/python3 ./anaconda -G --dirinstall /var/tmp/anaconda-install/ --repo http://example.com/repo cmdline_file: BOOT_IMAGE=/vmlinuz-4.3.0-0.rc5.git2.1.fc24.x86_64 root=/dev/mapper/fedora_tyan--gt24--05-root ro rd.lvm.lv=fedora_tyan-gt24-05/root rd.lvm.lv=fedora_tyan-gt24-05/swap console=ttyS0,115200 LANG=en_US.UTF-8 executable: ./anaconda hashmarkername: anaconda kernel: 4.3.0-0.rc5.git2.1.fc24.x86_64 other involved packages: python3-libs-3.4.3-5.fc24.x86_64 product: Fedora release: Fedora release 24 (Rawhide) type: anaconda version: rawhide
Created attachment 1087569 [details] File: anaconda-tb
Created attachment 1087570 [details] File: anaconda.log
Created attachment 1087571 [details] File: dnf.log
Created attachment 1087572 [details] File: dnf.rpm.log
Created attachment 1087573 [details] File: environ
Created attachment 1087574 [details] File: journalctl
Created attachment 1087575 [details] File: lsblk_output
Created attachment 1087576 [details] File: nmcli_dev_list
Created attachment 1087577 [details] File: os_info
Created attachment 1087578 [details] File: program.log
Created attachment 1087579 [details] File: storage.log
Created attachment 1087580 [details] File: packaging.log
Is selinux enabled? I see this in the logs: Oct 29 10:45:17 tyan-gt24-05.rhts.eng.bos.redhat.com audit[1111]: AVC avc: denied { sys_chroot } for pid=1111 comm="chpasswd" capability=18 scontext=unconfined_u:unconfined_r:passwd_t:s0-s0:c0.c1023 tcontext=unconfined_u:unconfined_r:passwd_t:s0-s0:c0.c1023 tclass=capability permissive=0
Yes, SELinux is enabled. The strange thing however is that this appears to work when I execute anaconda as /usr/sbin/anaconda and not when I execute if from a git checkout. Also it doesn't appear anaconda to modify /etc/ on the host system. It's strange that we get an avc denial in one case and not in the other. Btw I have resolved my other issues with running from a git checkout and will submit a patch tomorrow.
You should run it in permissive mode, running it from the checkout will confuse selinux which expects: system_u:object_r:install_exec_t:s0 /usr/sbin/anaconda*
Understood. Closing then.