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.
Comment 17Sankar Ramalingam
2014-09-11 18:07:59 UTC
Are there any steps to verify this bug? The clone of this bug #1034409 has been marked as Verified as Sanity only. Is that expected to be marked as Verified by IPA team?
We never could reproduce the original bug #1034409. We unfortunately did not file a specific bug for the specific problem that the fix for this bug caused in IPA. I suppose if 389-ds-base does not cause any regressions in IPA, then this bug can be verified.
Comment 19Sankar Ramalingam
2014-09-12 11:38:32 UTC
As per Rich's previous comment, I would expect the IPA team to mark it as Verified based on their regression/automated tests with the latest 389-ds-base-1.2.11.15-45.
Yes, the tests are looking much better and I've gotten good results back. As a result, I've run ipa-replica-install and ipa-replica-manage now many times and haven't seen this.
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.
http://rhn.redhat.com/errata/RHBA-2014-1385.html