samba - Apr 2013 - user both missing and present

I'm trying the classicupgrade, and it is crashing out:

ERROR(<class 'samba.provision.ProvisioningError'>): uncaught
exception -
ProvisioningError: Could not add member 'S-1-5-21-305843216-174882882-
1673945419-42545' to group 'S-1-5-21-305843216-174882882-1673945419-
1231' as either group or user record doesn't exist: Unable to find GUID
for DN
   File "/usr/local/samba/lib/python2.6/site-
packages/samba/netcmd/__init__.py", line 175, in _run
     return self.run(*args, **kwargs)
   File "/usr/local/samba/lib/python2.6/site-
packages/samba/netcmd/domain.py", line 1318, in run
     useeadb=eadb, dns_backend=dns_backend, use_ntvfs=use_ntvfs)
   File
"/usr/local/samba/lib/python2.6/site-packages/samba/upgrade.py",
line 919, in upgrade_from_samba3
     add_users_to_group(result.samdb, g, groupmembers[str(g.sid)],
logger)
   File
"/usr/local/samba/lib/python2.6/site-packages/samba/upgrade.py",
line 316, in add_users_to_group
     raise ProvisioningError("Could not add member '%s' to group
'%s' as
either group or user record doesn't exist: %s" % (member_sid,
group.sid,
emsg))


I've found that the user -42545 does not exist in my samba3 as a user, 
but somehow does exist as a member of the -1231 group.

I'm using the ldapsam passdb backend, and I don't understand how this 
situation has occurred. In my LDAP directory the -42545 user looks just 
like some of my other users (who don't trigger this problem).

What should I do next?

Cheers,
Geoff

On 17/04/13 13:46, Geoff Crompton wrote:
> I'm trying the classicupgrade, and it is crashing out:
<snip>
> I've found that the user -42545 does not exist in my samba3 as a user,
> but somehow does exist as a member of the -1231 group.
>
> I'm using the ldapsam passdb backend, and I don't understand how
this
> situation has occurred. In my LDAP directory the -42545 user looks just
> like some of my other users (who don't trigger this problem).
>
> What should I do next?
I found that my ldap server was limiting the number of objects returned 
to searches. The script didn't get details for the -42545 user when 
asking about all users, which explains my problem.

  Once I set that to 'unlimited' I got past this problem. I've made
a
note on 
https://wiki.samba.org/index.php/Samba4/samba-tool/domain/classicupgrade/HOWTO#Notes_about_migrating_from_LDAP_backend
for other people to watch out for that.

I wonder if the C library code behind the call to "s3db.search_users(0) 
in the upgrade_from_samba3() method of python/samba/upgrade.py should 
handle an LDAP server telling it the error condition that it's search 
has been limited (and then the python adaption could throw that up as an 
exception).

I've created bug 9808 ( https://bugzilla.samba.org/show_bug.cgi?id=9808 
) along those lines.

Cheers,
Geoff