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 1506913 - ipa-replica-install might fail because of an already existing entry cn=ipa-http-delegation,cn=s4u2proxy,cn=etc,$SUFFIX [rhel-7.4.z]
Summary: ipa-replica-install might fail because of an already existing entry cn=ipa-ht...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.4
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On: 1493145
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-27 07:13 UTC by Oneata Mircea Teodor
Modified: 2020-12-14 10:40 UTC (History)
11 users (show)

Fixed In Version: ipa-4.5.0-22.el7_4
Doc Type: If docs needed, set a value
Doc Text:
Cause – If a replica installation was done in the past and some info was left behind, the replication process may fail when applying replica-s4u2proxy.ldif. Consequence – The user would not be able to setup an IPA replica Fix – A verification is done to check if the needed values are already there. Result – The user is able to continue if the replication process.
Clone Of: 1493145
Environment:
Last Closed: 2017-11-30 16:01:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:3319 0 normal SHIPPED_LIVE ipa bug fix update 2017-11-30 20:18:30 UTC

Description Oneata Mircea Teodor 2017-10-27 07:13:00 UTC 
This bug has been copied from bug #1493145 and has been proposed to be backported to 7.4 z-stream (EUS).
Comment 2 Petr Vobornik 2017-10-27 15:21:12 UTC 
Fixed upstream

ipa-4-6:
https://pagure.io/freeipa/c/b3dfc13f36de365b78bfbf6ac0fda2549d134739

ipa-4-5:
https://pagure.io/freeipa/c/55b7f588d0eced7e4b7840d808138eb798347d77
Comment 7 Standa Laznicka 2017-11-06 08:32:55 UTC 
Answering the question on how to reproduce this:
There's an LDIF file that was previously used, with the following contents:

"""
dn: cn=ipa-http-delegation,cn=s4u2proxy,cn=etc,$SUFFIX
changetype: modify
add: memberPrincipal
memberPrincipal: HTTP/$FQDN@$REALM

# ipa-cifs-delegation-targets needs to be an ipaAllowedTarget for HTTP
# delegation but we don't add it here as an LDIF because this entry may
# already exist from another replica, or previous install. If it is missing
# then it will be caught by the update file 61-trusts-s4u2proxy.update

dn: cn=ipa-ldap-delegation-targets,cn=s4u2proxy,cn=etc,$SUFFIX
changetype: modify
add: memberPrincipal
memberPrincipal: ldap/$FQDN@$REALM
"""
Just perform ldapmodify with appropriately replaced variables on master server and try to install replica against such a master. Previously, the observed failure would happen, now the installation should pass.
Comment 9 Mohammad Rizwan 2017-11-07 14:50:13 UTC 
version:
ipa-server-4.5.0-22.el7_4.x86_64

Steps:

1. Added the entry for replica in directory server on master.

[root@master ~]# cat a.ldif 
dn: cn=ipa-http-delegation,cn=s4u2proxy,cn=etc,dc=testrelm,dc=test
changetype: modify
add: memberPrincipal
memberPrincipal: HTTP/replica.testrelm.test

dn: cn=ipa-ldap-delegation-targets,cn=s4u2proxy,cn=etc,dc=testrelm,dc=test
changetype: modify
add: memberPrincipal
memberPrincipal: ldap/replica.testrelm.test


[root@master ~]# ldapmodify -h master.testrelm.test -p 389 -D "cn=directory manager" -w Secret123 -f a.ldif 
modifying entry "cn=ipa-http-delegation,cn=s4u2proxy,cn=etc,dc=testrelm,dc=test"

modifying entry "cn=ipa-ldap-delegation-targets,cn=s4u2proxy,cn=etc,dc=testrelm,dc=test"

[root@master ~]#

2. Install replica


Expected result:
replica should install

Actual result:

Replica installed successfully.
Comment 13 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
Note You need to log in before you can comment on or make changes to this bug.