On 01/21/2016 11:26 AM, Ludwig Krispenz wrote:

On 01/21/2016 11:21 AM, thierry bordaz wrote:
On 01/21/2016 10:48 AM, Ludwig Krispenz wrote:

On 01/21/2016 10:30 AM, thierry bordaz wrote:

The fix look good.
Just a question, the target entry is checked with ipa_topo_check_entry_type. Is it equivalent to call ipa_topo_is_entry_managed ?
no, ipa_topo_check_entry_type() just determines if it is a segment, a host, to decide how to proceed. ipa_topo_is_entry_managed() would apply to an replication agreement to decide if both endpoints are managed servers ant that the suffix is managed

Ok thanks. In fact it does not apply to replica agreements.
It allows the modrdn to 'cn=masters' subtree. Is this subtree part of the topology config ?
no, it is probably not a good idea to move a master to another subtree, but it is not the task of the topology plugin to prevent this

Right. Thanks for all your explanations and patience. THe fix is good to me as well. Ack


On 01/21/2016 09:11 AM, Ludwig Krispenz wrote:

On 01/20/2016 05:45 PM, Martin Basti wrote:

On 11.12.2015 13:56, Ludwig Krispenz wrote:
Ticket: https://fedorahosted.org/freeipa/ticket/5536

Patch attached.

Patch works, I cannot move entry out of container via moddn operation.

I have question, is it expected to be able rename entry?
I tried it and I was able to change RDN
yes, that should be fine, it cannot change the connectivity.

#!CONNECTION ldap://vm-058-138.abc.idm.lab.eng.brq.redhat.com:636
#!DATE 2016-01-20T16:28:18.702
dn: cn=vm-058-137.abc.idm.lab.eng.brq.redhat.com-to-vm-058-138.abc.idm.lab.eng
changetype: moddn
newrdn: cn=vm-058-137.abc.idm.lab.eng.brq.redhat.com-to-vm-058-138.abc.idm.lab
deleteoldrdn: 1
newsuperior: cn=domain,cn=topology,cn=ipa,cn=etc,dc=dom-138,dc=abc,dc=idm,dc=l

Manage your subscription for the Freeipa-devel mailing list:
Contribute to FreeIPA: http://www.freeipa.org/page/Contribute/Code

Reply via email to