[ZOOKEEPER-3983] C client test suite hangs forever 'sss' is configured in /etc/nsswitch.conf

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.7.0
• Fix Version/s: 3.6.3, 3.7.0
• Component/s: c client, tests
• Labels: pull-request-available

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

• Assignee: Christopher Tubbs
• Reporter: Christopher Tubbs
• Created: 22/Oct/20 04:03
• Updated: 28/Mar/21 08:54
• Resolved: 22/Oct/20 07:53

Description

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).

Issue Links

• links to: GitHub Pull Request #1514