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 1399405 - replica install failed to load replica-s4u2proxy.ldif when master is older version of IPA
Summary: replica install failed to load replica-s4u2proxy.ldif when master is older ve...
Keywords:
Status: CLOSED DUPLICATE of bug 1400421
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: Kaleem
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-29 01:56 UTC by Scott Poore
Modified: 2016-12-09 17:11 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-09 17:11:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
ipareplica-install.log failure (7.40 KB, text/plain)
2016-11-29 01:56 UTC, Scott Poore 		no flags Details
View All

Description Scott Poore 2016-11-29 01:56:06 UTC 
Description of problem:

I'm installing an IPA Replica on RHEL7.3 when the IPA Master is running on RHEL 6.9.  Doing this, I see the following error:


  [31/42]: enabling S4U2Proxy delegation
ipa         : CRITICAL Failed to load replica-s4u2proxy.ldif: Command '/usr/bin/ldapmodify -v -f /tmp/tmpKO_zcx -H ldapi://%2fvar%2frun%2fslapd-EXAMPLE-COM.socket -x -D cn=Directory Manager -y /tmp/tmpRrluWB' returned non-zero exit status 1
  [32/42]: importing CA certificates from LDAP
  [error] DatabaseError: Operations error: 
Your system may be partly configured.
Run /usr/sbin/ipa-server-install --uninstall to clean up.

ipa.ipapython.install.cli.install_tool(Replica): ERROR    Operations error: 
ipa.ipapython.install.cli.install_tool(Replica): ERROR    The ipa-replica-install command failed. See /var/log/ipareplica-install.log for more information


Version-Release number of selected component (if applicable):

On Replica:

ipa-server-4.4.0-13.el7.x86_64

On Master:

ipa-server-3.0.0-51.el6.x86_64

How reproducible:
always.  I've seen this from automation and was easily able to reproduce manually.

Steps to Reproduce:
1.  Install ipa-server 3.0.0 on RHEL6 
2.  ipa-replica-prepare
3.  copy /usr/share/ipa/copy-schema-to-ca.py from replica to master and run
4.  ipa-replica-install --setup-ca --setup-dns ...

Actual results:
error as seen above.

Expected results:
no error and IPA installs.

Additional info:
Comment 1 Scott Poore 2016-11-29 01:56:47 UTC 
Created attachment 1225581 [details]
ipareplica-install.log failure
Comment 7 Petr Vobornik 2016-12-09 17:11:56 UTC 

*** This bug has been marked as a duplicate of bug 1400421 ***
Note You need to log in before you can comment on or make changes to this bug.