Bug 1108206

Summary: sshd should run at least once before ipa-client-install
Product: Red Hat Enterprise Linux 7 Reporter: Martin Kosek <mkosek>
Component: ipaAssignee: Martin Kosek <mkosek>
Status: CLOSED ERRATA QA Contact: Namita Soman <nsoman>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 7.1CC: rcritten, xdong
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ipa-4.0.3-1.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-05 10:11:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Martin Kosek 2014-06-11 14:48:26 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/4055

When `sshd` is not run before ipa-client-install is run (like in a kickstart), machine has no SSH keys generated and they are thus not uploaded to client host entry on FreeIPA server.

ipa-client-install man page should be updated to state that fact.

Comment 1 Martin Kosek 2014-06-11 15:23:29 UTC
This request is already fixed in upstream FreeIPA project. Please refer to the linked ticket for additional details and related commits.

Comment 3 Xiyang Dong 2015-01-05 19:33:14 UTC
Verified on ipa-client-4.1.0-13.el7.x86_64:

[root@qe-blade-05 ~]# man ipa-client
.
.
.

   Assumptions
       The ipa-client-install script assumes that the machine has already generated SSH keys. It will not gener‐
       ate SSH keys of its own accord. If SSH keys are not present (e.g when running the ipa-client-install in a
       kickstart, before ever running sshd), they will not be uploaded to the client host entry on the server.
.
.
.

Comment 5 errata-xmlrpc 2015-03-05 10:11:28 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0442.html