Bug 692914

Summary: ds-replication.spec calls "setup-ds.pl -u" in the %posttrans
Product: Red Hat Enterprise Linux 6 Reporter: Noriko Hosoi <nhosoi>
Component: 389-ds-baseAssignee: Rich Megginson <rmeggins>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: amsharma, ckannan, dpal, jgalipea
Target Milestone: rcKeywords: screened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ds-replication-1.2.8-0.10.rc5.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-19 10:41:44 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Attachments:
Description Flags
cvs diff DSRV-9-RHEL6/ds-replication.spec nhosoi: review?

Description Noriko Hosoi 2011-04-01 12:22:51 EDT
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
Comment 2 Amita Sharma 2011-05-10 04:08:19 EDT
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.
Comment 3 errata-xmlrpc 2011-05-19 10:41:44 EDT
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
Comment 4 Chandrasekar Kannan 2011-09-16 17:33:27 EDT
ds-replication is no longer a component of rhel. folding back to 389-ds-base.