[Freeipa-devel] [PATCH] 0080 Sync in both direction before changing replication agreement in replica

Simo Sorce ssorce at redhat.com
Tue Feb 1 18:51:25 UTC 2011


On Tue, 1 Feb 2011 07:39:14 -0500
Simo Sorce <ssorce at redhat.com> wrote:

> On Mon, 31 Jan 2011 23:07:24 -0500
> Rob Crittenden <rcritten at redhat.com> wrote:
> 
> > Simo Sorce wrote:
> > > On Mon, 31 Jan 2011 18:38:47 -0500
> > > Simo Sorce<ssorce at redhat.com>  wrote:
> > >
> > >>
> > >> See also ticket #887
> > >>
> > >> Simo.
> > >>
> > >
> > > With a patch file it works better I guess :-)
> > >
> > > Simo.
> > >
> > >
> > 
> > I wasn't entirely sure how to test this so I use ipa-replica-manage 
> > re-initialize --from=master.example.com
> > 
> > It seemed to work, not sure how I can really tell. I did notice this
> > in my 389-ds error log:
> > 
> > [31/Jan/2011:23:05:59 -0500] - import userRoot: Import complete. 
> > Processed 159 entries in 4 seconds. (39.75 entries/sec)
> > [31/Jan/2011:23:06:00 -0500] NSMMReplicationPlugin - 
> > multimaster_be_state_change: replica dc=example,dc=com is coming
> > online; enabling replication
> > [31/Jan/2011:23:06:00 -0500] NSMMReplicationPlugin -
> > replica_reload_ruv: Warning: new data for replica dc=example,dc=com
> > does not match the data in the changelog.
> >   Recreating the changelog file. This could affect replication with 
> > replica's  consumers in which case the consumers should be
> > reinitialized.
> > 
> > rob
> 
> I changed force-sync not re-inititialize :-)
> 
> And the actual real change happend in ipa-replica-install
> So the way to test it would be to install a replica and make sure it
> works (I tested it on my side and it did).

Acked in private by Rob and pushed to master.

Simo.

-- 
Simo Sorce * Red Hat, Inc * New York




More information about the Freeipa-devel mailing list