CTDB and 4.1

Amitay Isaacs amitay at gmail.com
Thu Jun 27 18:51:27 MDT 2013


On Fri, Jun 28, 2013 at 8:53 AM, Andrew Bartlett <abartlet at samba.org> wrote:

> On Fri, 2013-06-28 at 00:18 +0200, Christian Ambach wrote:
> > Am 27.06.13 10:38, schrieb Karolin Seeger:
> > > Hi list,
> > >
> > > this is a reminder that Samba 4.1.0rc1 is scheduled for Thursday, July
> 11
> > > 2013. That means, the v4-1-test branch will be synced with the master
> > > branch on Thursday, July 4 and closed after that. Only bug fixes with
> > > corresponding bug reports will be picked for the release branches after
> > > this date.
> > >
> > > There is a meta bug report containing all blocker bugs for 4.1.0:
> > >
> > >    https://bugzilla.samba.org/show_bug.cgi?id=9306
> >
> > One thing that is currently severly broken in master is running with
> > CTDB. dbwrap_ctdb and dbwrap_tdb have different semantics when it comes
> > to deleted records that break code at multiple places and lead not only
> > to ugly messages spammed into the logs but also to functional breakage.
> > I have discussed this with Michael and Amitay on SambaXP and we know how
> > to approach it, but we haven't found the time to fix it yet.
> >
> > So I see this as something that really needs to be fixed before it gets
> > released, however as there is no "master" version in Bugzilla that I
> > could use to report this (as this is new breakage that is not in 4.0).
> >
> > How should this be dealt with?
>
> Don't let bugzilla categories stop you.  Reporting against an unreleased
> version of 4.0 is fine, just clarify stuff in the bug.
>
> When can we expect to see the CTDB tree merge back in, and will we have
> tests to detect this kind of issue?
>
>
CTDB would be merged for 4.2. So once 4.1 tree is frozen, I can start
working on the merge.

Amitay.


More information about the samba-technical mailing list