Hide Forgot
Description of problem: 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:
https://fedorahosted.org/freeipa/ticket/1174
Thank you taking your time and submitting this request for Red Hat Enterprise Linux. Unfortunately, this bug was not given a priority and was deferred both in the upstream project and in Red Hat Enterprise Linux. Given that we are unable to fulfill this request in following Red Hat Enterprise Linux releases, I am closing the Bugzilla as DEFERRED. To request that Red Hat re-considers the decision, please re-open the Bugzilla via appropriate support channels and provide additional business and/or technical details about its importance to you. Note that you can still track this request or even contribute patches in the referred upstream Trac ticket.