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.
DescriptionLukas Slebodnik
2019-05-01 14:40:28 UTC
Description of problem:
The latest update of 389-ds-base cause failures with setup of ipa replica
Version-Release number of selected component (if applicable):
389-ds-base-1.3.9.1-5.el7.x86_64
How reproducible:
Deterministic
Steps to Reproduce:
1. # install ipa-server on one machine
2. # try to install replica on another machine
e.g.
/usr/sbin/ipa-replica-install -U --setup-ca --setup-dns -P admin -w Secret123
Actual results:
[15/41]: configuring DNS plugin
[16/41]: enabling entryUSN plugin
[17/41]: configuring lockout plugin
[18/41]: configuring topology plugin
[19/41]: creating indices
[20/41]: enabling referential integrity plugin
[21/41]: configuring certmap.conf
[22/41]: configure new location for managed entries
[23/41]: configure dirsrv ccache
[24/41]: enabling SASL mapping fallback
[25/41]: restarting directory server
[26/41]: creating DS keytab
[error] NetworkError: cannot connect to 'ldaps://ibm-x3250m4-05.testrelm.test':
ipapython.admintool: ERROR cannot connect to 'ldaps://ibm-x3250m4-05.testrelm.test':
ipapython.admintool: ERROR The ipa-replica-install command failed. See /var/log/ipareplica-install.log for more information
Your system may be partly configured.
Run /usr/sbin/ipa-server-install --uninstall to clean up.
Expected results:
Replica installed without any problem
ipa version: ipa-server-4.6.5-8.el7.x86_64
389-ds package: 389-ds-base-1.3.9.1-6.el7.x86_64
Verified the bug on the basis of following observations:
1. Verified that replica installation is successful.
2. Verified that the FIALURES observed at comment#11 are no more observed, re-ran jobs thrice and all the three occasion replica installation is successful.
Thus on the basis of above observations , marking bug to "VERIFIED"
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2019:2152