https://bugzilla.redhat.com/show_bug.cgi?id=695797
When installing client in a master-slave config, an invalid host record was created for client, when testing failover.
Installed client successfully a few times in a master-slave environment going against both servers Next ran ipactl stop on master, and installed client against replica. Then started ipa services on master, stopped ipa services on slave, and uninstalled. Started services on replica, and installed client. this failed with error that - RPC failed at server. Constraint violation: Another entry with the same attribute value already exists (attribute: "krbPrincipalName")
Joining realm failed because of failing XML-RPC request. This error may be caused by incompatible server/client major versions.
running ipa host-find lists this client but running host-del - says - host not found
ldapsearch listed this client as - fqdn=rhel61-client3.testrelm+nsuniqueid=807bb87f-652211e0-9e848fb2-f0f04a39,cn=computers,cn=accounts,dc=testrelm
Version-Release number of selected component (if applicable): ipa-server-2.0.0-20.el6.x86_64
How reproducible:
Steps to Reproduce: 1.install master-slave 2. stop master, install client 3. start master, stop slave, uninstall client 4. start slave, install client
Actual results: client install fails with error - Joining realm failed because of failing XML-RPC request. This error may be caused by incompatible server/client major versions.
Expected results: client install should be successful
Additional info:
The problem is caused by a replication conflict in DS. The solution will be related to #1025 planned for 2.2.
RFE for 389-ds replication improvement: https://bugzilla.redhat.com/show_bug.cgi?id=747701
Moving the ticket to the next month iteration.
This is the same case as ticket #1025. Moving to 3.1.
Moving my tickets back to free-to-take pool.
Metadata Update from @dpal: - Issue assigned to someone - Issue set to the milestone: Ticket Backlog
This will be handled by replication conflict management and we don't need to track this directly as a use-case.
Metadata Update from @rcritten: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.