Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
removing a ipa replica from the master causes failure messages, then, IPA on the master becomes unresponsive until IPA is restarted,
Version-Release number of selected component (if applicable):
ipa-server-3.3.3-6.el7.x86_64
389-ds-base-1.3.1.6-12.el7.x86_64
How reproducible:
unknown
Steps to Reproduce:
1. Install IPA
2. prepare replica file
3. install ipa replica
4. ipa-replica-manage del <replica>
5. Other IPA commands will not work on the master until the user restarts ipa.
Actual results:
[root@nocp7 ~]# ipa-replica-manage del nu4.testrelm.com
Directory Manager password:
Deleting a master is irreversible.
To reconnect to the remote master you will need to prepare a new replica file
and re-install.
Continue to delete? [no]: yes
Deleting replication agreements between nu4.testrelm.com and nocp7.testrelm.com
ipa: INFO: Setting agreement cn=meTonocp7.testrelm.com,cn=replica,cn=dc\=testrelm\,dc\=com,cn=mapping tree,cn=config schedule to 2358-2359 0 to force synch
ipa: INFO: Deleting schedule 2358-2359 0 from agreement cn=meTonocp7.testrelm.com,cn=replica,cn=dc\=testrelm\,dc\=com,cn=mapping tree,cn=config
ipa: INFO: Replication Update in progress: TRUE: status: 0 Replica acquired successfully: Incremental update started: start: 0: end: 0
ipa: INFO: Replication Update in progress: FALSE: status: 0 Replica acquired successfully: Incremental update succeeded: start: 0: end: 0
Unable to remove agreement on nu4.testrelm.com: cannot connect to 'ldaps://nu4.testrelm.com:636':
Forcing removal on 'nocp7.testrelm.com'
Any DNA range on 'nu4.testrelm.com' will be lost
There were issues removing a connection for nu4.testrelm.com from nocp7.testrelm.com: cannot connect to 'ldaps://nocp7.testrelm.com:636':
unexpected error: cannot connect to 'ldaps://nocp7.testrelm.com:636':
[root@nocp7 ~]# ipa-replica-manage list
Connection timed out.
Additional info:
There does not seem to be much helpful in the logs on this one.
Additionally, after IPA is restarted, the replica still seems to be around.
[root@nocp7 ~]# ipa-replica-manage list
Directory Manager password:
nu4.testrelm.com: master
nocp7.testrelm.com: master
Adding -cf also seems to create the same behaviour:
[root@nocp7 ~]# ipa-replica-manage del nu4.testrelm.com -cf
Directory Manager password:
Connection to 'nu4.testrelm.com' failed:
Forcing removal of nu4.testrelm.com
Skipping calculation to determine if one or more masters would be orphaned.
Deleting replication agreements between nu4.testrelm.com and nocp7.testrelm.com
Failed to get list of agreements from 'nu4.testrelm.com':
Forcing removal on 'nocp7.testrelm.com'
Any DNA range on 'nu4.testrelm.com' will be lost
There were issues removing a connection for nu4.testrelm.com from nocp7.testrelm.com: cannot connect to 'ldaps://nocp7.testrelm.com:636':
unexpected error: cannot connect to 'ldaps://nocp7.testrelm.com:636':
[root@nocp7 ~]# ipa-replica-manage list
Connection timed out.
[root@nocp7 ~]# ipactl stop
Stopping Directory Service
Stopping ipa-otpd Service
Stopping pki-tomcatd Service
Stopping httpd Service
ipacStopping ipa_memcached Service
Stopping named Service
tStopping kadmin Service
Stopping krb5kdc Service
ipa: INFO: The ipactl command was successful
l[root@nocp7 ~]# ipactl start
Starting Directory Service
Starting krb5kdc Service
Starting kadmin Service
Starting named Service
Starting ipa_memcached Service
Starting httpd Service
Starting pki-tomcatd Service
Starting ipa-otpd Service
ipa: INFO: The ipactl command was successful
[root@nocp7 ~]# ipa-replica-manage list
Directory Manager password:
nu4.testrelm.com: master
nocp7.testrelm.com: master
You have new mail in /var/spool/mail/root
I think you hit a known bug when DS crashed when replicas were being manipulated (probably Bug 1049522, adding Noriko to CC list to know about this one).
Michael, can you please try the test with 389-ds-base-1.3.1.6-14.el7? The crash should be fixed here as you can read in Bug 1049522. I run a quick test with this DS version and I do not see the crash any more.