Bug 7486 - Support unprovisioned environments for RPC-SPOOLSS-NOTIFY
Summary: Support unprovisioned environments for RPC-SPOOLSS-NOTIFY
Status: RESOLVED FIXED
Alias: None
Product: Samba 4.0
Classification: Unclassified
Component: smbtorture (show other bugs)
Version: unspecified
Hardware: Other Linux
: P3 major (vote)
Target Milestone: ---
Assignee: Andrew Bartlett
QA Contact: samba4-qa@samba.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-01 17:11 UTC by Guenther Deschner
Modified: 2010-08-18 10:53 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Guenther Deschner 2010-06-01 17:11:01 UTC
when I start an unprovisioned s4 samba and try

   smbclient -L localhost -U%

I get: session setup failed: NT_STATUS_INTERNAL_DB_CORRUPTION

This is problematic (and probably a regression) as the RPC-SPOOLSS-NOTIFY test when run against s3 during make test starts an unprovisioned spoolss rpc server for changenotify backchannel communication.
Comment 1 Andrew Bartlett 2010-06-01 17:47:43 UTC
Urgh.  I would rather not support an un-provisioned server, as that will constantly hit this kind of issue, so the correct fix will be for smbtorture to provision locally in a tmp dir before it starts the listener. 

(The actual change for this was the work to support nested groups and aliases properly - this could be hacked around, but I would rather not).
Comment 2 Andrew Bartlett 2010-06-02 01:04:01 UTC
I've been on a good bike ride, and changed my mind.

We should support this, because the 'general case' gets the answer wrong anyway.  When I eventually get around to writing python tests for tokenGroups, it will show that anonymous has no extra SIDs.  

We should therefore hard code this case, which will also fix this problem. 
Comment 3 Andrew Bartlett 2010-06-07 19:28:18 UTC
The fact that this breaks the spoolss tests make this a major issue, which I intend to resolve soon. 
Comment 4 Guenther Deschner 2010-08-18 08:05:40 UTC
This one can be closed then ?
Comment 5 Matthias Dieter Wallnöfer 2010-08-18 10:53:44 UTC
Well, I close it with "FIXED" - if abartlet still prefers to have it around he can always reopen (very unlikely I would say).