Bug 1489300

Summary: Unable to set ca renewal master on replica [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: high Docs Contact:
Priority: high    
Version: 7.4CC: akasurde, fbarreto, frenaud, ipa-maint, ksiddiqu, lkimlick, pvoborni, pvomacka, rcritten, slaznick, tscherf
Target Milestone: rcKeywords: Regression, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ipa-4.5.0-21.el7.2 Doc Type: If docs needed, set a value
Doc Text:
* Previously, the "ipa config-mod --ca-renewal-master-server hostname" command failed on a replica. Consequently, the administrator could not configure the replica as Certificate Authority renewal master. To fix this bug, the parameters were passed in expected format. As a result, using the "ipa config-mod--ca-renewal-master-server hostname" command is now successful.
 Story Points: ---
Clone Of: 1482802 Environment:
Last Closed: 2017-10-19 15:12:49 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: 1482802    
Bug Blocks:    
Attachments:
Description Flags
console.log none

Description Oneata Mircea Teodor 2017-09-07 07:27:40 UTC 
This bug has been copied from bug #1482802 and has been proposed to be backported to 7.4 z-stream (EUS).
Comment 4 Oneata Mircea Teodor 2017-09-07 07:29:19 UTC 
*** Bug 1489299 has been marked as a duplicate of this bug. ***
Comment 6 Abhijeet Kasurde 2017-09-22 09:40:19 UTC 
Verified using IPA version :: 

ipa-server-4.5.0-21.el7_4.2.x86_64

Marking BZ as verified. Please find attachment as console.log.
Comment 7 Abhijeet Kasurde 2017-09-22 09:41:22 UTC 
Created attachment 1329500 [details]
console.log
Comment 10 errata-xmlrpc 2017-10-19 15:12:49 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:2935