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.

Created attachment 489428 [details]
cvs diff DSRV-9-RHEL6/ds-replication.spec

Description of problem:
On 03/31/2011 05:41 PM, Rich Megginson wrote:
> We could add a %posttrans to ds-replication - it would be nice if we could figure out a way, if you are installing/upgrading both 389-ds-base and ds-replication, to only run setup-ds.pl once - if it is run twice that should be ok, it will bounce the servers twice - it would be nice to figure out a way, in the %posttrans of ds-replication, to do something like this
>
> if ! [ 389-ds-base is in package list ] ; then
>     setup-ds.pl -u
> fi

I copied the %posttrans section from 389-ds-base.spec and rebuilt ds-replication package.  It seems the section is perfect for ds-replication, too.  I could configure MMR without the manual running "setup-ds.pl -u".

This scenario works fine:
1) install 389-ds-base
2) setup instance
3) install ds-replication
4) try to setup replication in existing instance

I also ran extra "setup-ds.pl -u" after (3).  There's no problem if  taking the following steps, too.
1) install 389-ds-base
2) setup instance
3) install ds-replication
3-1) setup-ds.pl -u
4) try to setup replication in existing instance

I have upgraded my ds setup using setup-ds.pl -u after upgrading the new brew builds for 389-ds-base and replication packages.
And successfully verified many replication related issues.

So, I think this covers this bug verification.
Hence Marking the bug as VERIFIED.

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2011-0820.html

ds-replication is no longer a component of rhel. folding back to 389-ds-base.