Description of problem: The root account misses the usual skel items. This renders the root account not being configured properly. As a side-effect some automation/orchestration frameworks might require atomic-specific workaround. In my case, automation fails to detect the fall-back prompt: "bash-4.3# " I've also noticed the /root directory is a symlink into /var/roothome which I think might be related. bash-4.3# rpm -qf /root/ filesystem-3.2-27.fc21.x86_64 bash-4.3# bash-4.3# ls -la /root/ total 20 drwx------. 3 root root 4096 Nov 19 10:48 . drwxr-xr-x. 23 root root 4096 Nov 19 10:48 .. -rw-------. 1 root root 7171 Oct 29 10:09 anaconda-ks.cfg drwx------. 2 root root 4096 Nov 19 10:48 .ssh bash-4.3# Version-Release number of selected component (if applicable): F21 Beta; EC2; eu-central-1; ami-4ccef851; filesystem-3.2-27.fc21.x86_64 How reproducible: Always Steps to Reproduce: 1. instantiate ami 2. log-in fedora user 3. sudo su - Actual results: system-wide skel settings not applied to root account Expected results: system-wide skel settings applied to root account Additional info: Project Atomic question: http://ask.projectatomic.io/en/question/141/root-home-missing-usual-skel-items/ Project Atomic similar discussion: https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2014-November/msg00052.html
Do you have an example of an automation/orchestration system where things don't work because of this configuration?
(In reply to Joe Brockmeier from comment #1) > Do you have an example of an automation/orchestration system where things > don't work because of this configuration? https://github.com/RedHatQE/dva ; where Paramiko failed to detect the prompt in root account; workaround: https://github.com/RedHatQE/dva/commit/d666f2607685f59fed6c6ed9f5bc0787451c6475#diff-d33064dcda1fcd69d95177adc753d69eR151
See https://bugzilla.redhat.com/show_bug.cgi?id=1193590
*** This bug has been marked as a duplicate of bug 1193590 ***