Bug 13225 - ad_member testenv fails to start, as createbuiltingroup cannot find winbind
ad_member testenv fails to start, as createbuiltingroup cannot find winbind
Status: NEW
Product: Samba 4.1 and newer
Classification: Unclassified
Component: Test infrastructure
4.8.0rc1
All All
: P5 minor
: ---
Assigned To: Jelmer Vernooij
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-01-15 21:37 UTC by Jamie McClymont
Modified: 2018-02-11 16:00 UTC (History)
2 users (show)

See Also:


Attachments
Resolves by adding NSS_WRAPPER variables to the net calls (1.52 KB, patch)
2018-01-15 21:37 UTC, Jamie McClymont
no flags Details
Patches for v4-8-test (1.86 KB, patch)
2018-02-11 11:46 UTC, Stefan Metzmacher
slow: review-
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jamie McClymont 2018-01-15 21:37:07 UTC
Created attachment 13906 [details]
Resolves by adding NSS_WRAPPER variables to the net calls

The ad_member environment fails to start, logging:

>> winbind seems not to run. createbuiltingroup only works when winbind runs.

Andreas explains the issue on samba-technical:

> libwbclient needs to connect to the winbind socket. To find the winbind socket 
> inside of selftest it uses:
>
>   if (nss_wrapper_enabled()) {
>           env_dir = getenv("SELFTEST_WINBINDD_SOCKET_DIR");
>   }
>
> So we need the NSS_WRAPPER variables to "enable" nss_wrapper. This way wbinfo 
> connects to the right winbindd ...
Comment 1 Stefan Metzmacher 2018-02-11 11:46:18 UTC
Created attachment 13952 [details]
Patches for v4-8-test
Comment 2 Ralph Böhme 2018-02-11 16:00:19 UTC
Comment on attachment 13952 [details]
Patches for v4-8-test

This is part of the backport in bug #13265.