Bug 1284717 - On RHEL 7.2 environments, ssh access fails when a user is created using the 'user' module
On RHEL 7.2 environments, ssh access fails when a user is created using the '...
Status: NEW
Product: khaleesi
Classification: Community
Component: rdo-manager (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: wes hayutin
Attila Darazs
: Automation, AutomationBlocker
Depends On:
  Show dependency treegraph
Reported: 2015-11-23 19:52 EST by Ronelle Landy
Modified: 2018-01-29 21:56 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ronelle Landy 2015-11-23 19:52:33 EST
Description of problem:

On RHEL 7.2 platforms, executing:
user: name="<user-name>" state=present password=<user-password> creates the user but trying to ssh to the host with that user will fail.
The following warning is seen:

useradd: warning: the home directory already exists.
Not copying any file from skel directory into it.

Version-Release number of selected component (if applicable):

RHEL 7.2 (RC 1-1)
Ansible 1.9.2

How reproducible:

Always on baremetal environments
Sometimes on vrt env when reprovisioning is done prior

Steps to Reproduce:
1. Install RHEL 7.2 (RC 1-1) on a host machine
2. Run an Ansible playbook that create a user like: 
user: name="<user-name>" state=present password=<user-password>
3. ssh from a remote host to the host machine as the user created

Actual results:

ssh fail authentication

Expected results:

should be able to ssh into the host machine when a user is created with reqired passwors or key files

Additional info:


      shell: >
        userdel -f <user>;
        rm -rf /home/<user>;
        useradd <user>


user: name="<user>" state=absent password=<user password> 
user: name="<user>" state=present password=<user password>

Note You need to log in before you can comment on or make changes to this bug.