[
https://issues.apache.org/jira/browse/ZOOKEEPER-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mate Szalay-Beko resolved ZOOKEEPER-3983.
-----------------------------------------
Fix Version/s: 3.6.3
3.7.0
Resolution: Fixed
Issue resolved by pull request 1514
[https://github.com/apache/zookeeper/pull/1514]
> C client test suite hangs forever 'sss' is configured in /etc/nsswitch.conf
> ---------------------------------------------------------------------------
>
> Key: ZOOKEEPER-3983
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3983
> Project: ZooKeeper
> Issue Type: Bug
> Components: c client, tests
> Affects Versions: 3.7.0
> Environment: Fedora 32 x86_64
> default /etc/nsswitch.conf file (provided by glibc package)
> sssd services are not running, but sss does appear above files in the
> 'passwd' entry
> Reporter: Christopher Tubbs
> Assignee: Christopher Tubbs
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.7.0, 3.6.3
>
> Attachments: backtrace.txt, workaround.patch
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> While testing a full build on the master branch (3.7.0-SNAPSHOT), I observed
> that the C client tests hang indefinitely when reaching the zktest-mt's
> Zookeeper_close test suite (nothing is printed from that suite, but
> Zookeeper_init finishes and then nothing is printed)
> Attaching gdb as a debugger to the zktest-mt process, with the help of
> [~ztzg] and [~symat] I saw that it was stuck in the sss because of the test
> mocking sockets, and sss requiring a non-mocked socket to call getpwuid_r and
> getlogin functions in zookeeper-client/zookeeper-client-c/src/zookeeper.c
> Disabling the lines in zookeeper.c that called those functions, which seemed
> to be used for logging information only, the tests were able to proceed and
> complete in under 9 minutes (full-build, without running any surefire/junit
> tests).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
