Bug 1506528

Summary: In case full PKINIT configuration is failing during server/replica install the error message should be more meaningful. [rhel-7.4.z]
Product: Red Hat Enterprise Linux 7 Reporter: Oneata Mircea Teodor <toneata>
Component: ipaAssignee: IPA Maintainers <ipa-maint>
Status: CLOSED ERRATA QA Contact: ipa-qe <ipa-qe>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 7.4CC: aslaikov, fbarreto, ipa-maint, ksiddiqu, msauton, ppicka, pvoborni, pvomacka, rcritten, tkrizek, tscherf
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: ipa-4.5.0-22.el7_4 Doc Type: If docs needed, set a value
Doc Text:
Cause – CA is not reachable Consequence – confusing error message Fix – changed log level from error to warning; added message Result – Less confusing message
Story Points: ---
Clone Of: 1493531 Environment:
Last Closed: 2017-11-30 16:01:44 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:
Bug Depends On: 1493531    
Bug Blocks:    

Description Oneata Mircea Teodor 2017-10-26 09:37:08 UTC
This bug has been copied from bug #1493531 and has been proposed to be backported to 7.4 z-stream (EUS).

Comment 4 Pavel Picka 2017-11-07 11:15:55 UTC
verified on ipa-server-4.5.0-22.el7_4.x86_64

...
 [1/1]: installing X509 Certificate for PKINIT
Full PKINIT configuration did not succeed
The setup will only install bits essential to the server functionality
You can enable PKINIT after the setup completed using 'ipa-pkinit-manage'
Done configuring Kerberos KDC (krb5kdc).
Applying LDAP updates
Upgrading IPA:. Estimated time: 1 minute 30 seconds
  [1/9]: stopping directory server
...

Comment 8 errata-xmlrpc 2017-11-30 16:01:44 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://access.redhat.com/errata/RHBA-2017:3319