freeipa

#6470 Failed replica installation under domlevel 0 throws user into debugger shell
Closed: Invalid Opened by ofayans.

Closed: Invalid
Reopen Issue 
[root@vm-058-210 ~]# ipa-replica-install -w <admin_pass> -p <dirman_pass> ./replica-info-vm-058-210.dom-058-121.<lab_fqdn>.gpg 
WARNING: conflicting time&date synchronization service 'chronyd' will
be disabled in favor of ntpd
This replica was created for 'vm-058-210.dom-058-121.<lab_fqdn>' but this machine is named 'vm-058-210.<lab_fqdn>'
This may cause problems. Continue? [no]: yes
> /usr/lib/python2.7/site-packages/ipaserver/plugins/ldap2.py(153)create_connection()
-> if bind_dn is None:
(Pdb)

Steps to reproduce[[BR]]
1. Install a master with domain level 0
2. On master prepare a replica file for a replica with hostname different than the hostname of the machine you intend to use as replica.
3. Copy replica gpg file over to replica host
4. On a replica host install replica using the copied file

What git build/version of rpm?

I tried to reproduce this with clean VMs and fresh build+install from current master (33f7b8dc32bc95e0db067ac4df49807ee2b5120e) and I haven't run into this issue. I also didn't find pdb anywhere in the current code.

This may be caused by some improper clean up or reused VMs.

Metadata Update from @ofayans:
- Issue assigned to someone
- Issue set to the milestone: 0.0 NEEDS_TRIAGE
Metadata
None
None
None
Normal
defect
IPA
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.