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 814792 - Replication errors when CS and DS share a database
Summary: Replication errors when CS and DS share a database
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-Linux_Domain_Identity_Management_Guide
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Aneta Šteflová Petrová
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-20 17:08 UTC by Deon Ballard
Modified: 2019-03-06 01:20 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-10 12:05:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Deon Ballard 2012-04-20 17:08:31 UTC
This is something that we need to revisit when the CS and IPA start sharing same DS instance. 

 https://bugzilla.redhat.com/show_bug.cgi?id=750529 

Description of problem:
After CS replication is removed, replica can see a new host is issued a cert,
but doesn't have a copy of it, and throws a serial number error.

In response to a test case to do this, Rob's response:
I wonder if we should doc this. What is happening is the host is
replicating through a different channel, so we can see it. Because the
CS replication was removed we can see that the host has been issued a
valid certificate from our CA but our local install doesn't have a copy
of it, hence the serial # error.

This and a few others point out some pretty scary problems related to
certificate replication, this isn't something people should take lightly.

Version-Release number of selected component (if applicable):
ipa-server-2.1.3-6.el6.x86_64


How reproducible:
always

Steps to Reproduce:
1.Install master, replica
2.Install CS server on replica
3.Delete the replication agreement, and the data from replica
# ipa-csreplica-manage del ipa-replica1.testrelm -p XXX
4. Add a host, add cert to a host from master
5. Check settings for this host from replica

Actual results:
Error that host?s cert cannot be found:
Certificate operation cannot be completed: EXCEPTION (Certificate serial number
0x2d not found)

Expected results:
if this is doc'd, the user will know to check CS replication, and be prepared.

Comment 1 Deon Ballard 2012-04-20 17:09:26 UTC
This is from https://fedorahosted.org/freeipa/ticket/2047.

Comment 2 Deon Ballard 2012-11-07 21:57:26 UTC
This is not in RHEL 6.4. Unsetting the flags.

Comment 4 Deon Ballard 2013-02-06 19:34:52 UTC
Changing to RHEL 7.

Comment 8 Scott Poore 2015-02-12 19:36:54 UTC
document verified.


Note You need to log in before you can comment on or make changes to this bug.