RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1207649 - host certificate not issued to client during ipa-client-install
Summary: host certificate not issued to client during ipa-client-install
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ipa
Version: 6.7
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Jan Cholasta
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-31 12:20 UTC by Kaleem
Modified: 2015-07-22 07:39 UTC (History)
4 users (show)

Fixed In Version: ipa-3.0.0-46.el6
Doc Type: Bug Fix
Doc Text:
Regression bug fix, do not document.
Clone Of:
Environment:
Last Closed: 2015-07-22 07:39:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
console output with snip from error_log from IPA Server (5.62 KB, text/plain)
2015-03-31 12:20 UTC, Kaleem 		no flags Details
Fix (1.66 KB, patch)
2015-04-08 12:47 UTC, Jan Cholasta 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1462 0 normal SHIPPED_LIVE Moderate: ipa security and bug fix update 2015-07-21 14:14:52 UTC

Description Kaleem 2015-03-31 12:20:31 UTC 
Created attachment 1008994 [details]
console output with snip from error_log from IPA Server

Description of problem:
During ipa-client-install host certificate is not issued to client and complaining about the host record not found on IPA server for SAN in certificate request.

	ca-error: Server at https://dhcp207-188.testrelm.test/ipa/xml failed request, will retry: 4001 (RPC failed at server.  no host record for subject alt name host/dhcp207-3.testrelm.test in certificate request).

Version-Release number of selected component (if applicable):
[root@dhcp207-3 ~]# rpm -q ipa-client certmonger
ipa-client-3.0.0-45.el6.x86_64
certmonger-0.77.1-1.el6.x86_64
[root@dhcp207-3 ~]#


How reproducible:
Always

Steps to Reproduce:
1. Run ipa-client-install
2. Run "getcert list" to check host certificate issued to host


Actual results:
Host Certificate not issued

Expected results:
Host certificate should have been issued

Additional info:
(1)Please find the attached console output on client and snip from /var/log/httpd/error_log on IPA Server.
Comment 3 Jan Cholasta 2015-04-08 12:47:19 UTC 
Created attachment 1012224 [details]
Fix

Attached a patch with a fix.

Note that this is caused by the fix for bug 1154776.
Comment 5 Kaleem 2015-04-22 04:31:01 UTC 
Verified.

IPA Version:
============
On Server:

[root@dhcp207-230 ~]# rpm -q ipa-server pki-ca
ipa-server-3.0.0-46.el6.x86_64
pki-ca-9.0.3-41.el6.noarch
[root@dhcp207-230 ~]# 

On Client:

[root@dhcp207-223 ~]# rpm -q ipa-client certmonger
ipa-client-3.0.0-46.el6.x86_64
certmonger-0.77.2-1.el6.x86_64
[root@dhcp207-223 ~]#

Console output snip:
====================
[root@dhcp207-223 ~]# ipa-client-install  -U --domain=testrelm.test --realm=TESTRELM.TEST -p admin -w xxxxxxxx --server=dhcp207-230.testrelm.test
Hostname: dhcp207-223.testrelm.test
Realm: TESTRELM.TEST
DNS Domain: testrelm.test
IPA Server: dhcp207-230.testrelm.test
BaseDN: dc=testrelm,dc=test

Synchronizing time with KDC...
Successfully retrieved CA cert
    Subject:     CN=Certificate Authority,O=TESTRELM.TEST
    Issuer:      CN=Certificate Authority,O=TESTRELM.TEST
    Valid From:  Tue Apr 21 15:20:44 2015 UTC
    Valid Until: Sat Apr 21 15:20:44 2035 UTC

Enrolled in IPA realm TESTRELM.TEST
Attempting to get host TGT...
.....
SSSD enabled
Configuring testrelm.test as NIS domain
Configured /etc/openldap/ldap.conf
NTP enabled
Configured /etc/ssh/ssh_config
Configured /etc/ssh/sshd_config
Client configuration complete.
[root@dhcp207-223 ~]# ipa-getcert list
Number of certificates and requests being tracked: 1.
Request ID '20150422070325':
	status: MONITORING
	stuck: no
	key pair storage: type=NSSDB,location='/etc/pki/nssdb',nickname='IPA Machine Certificate - dhcp207-223.testrelm.test',token='NSS Certificate DB'
	certificate: type=NSSDB,location='/etc/pki/nssdb',nickname='IPA Machine Certificate - dhcp207-223.testrelm.test',token='NSS Certificate DB'
	CA: IPA
	issuer: CN=Certificate Authority,O=TESTRELM.TEST
	subject: CN=dhcp207-223.testrelm.test,O=TESTRELM.TEST
	expires: 2017-04-22 07:03:26 UTC
	key usage: digitalSignature,nonRepudiation,keyEncipherment,dataEncipherment
	eku: id-kp-serverAuth,id-kp-clientAuth
	pre-save command: 
	post-save command: 
	track: yes
	auto-renew: yes
[root@dhcp207-223 ~]#
Comment 7 errata-xmlrpc 2015-07-22 07:39:54 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-1462.html
Note You need to log in before you can comment on or make changes to this bug.