We should backport this patch in preparation of a potential future fix for bug 132608 later in the life-cycle of Red Hat Enterprise Linux 8. commit a9368c34d70cef91ca59b09941f496df11d6b146 Author: Florian Weimer <fweimer> Date: Wed May 15 13:51:35 2019 +0200 nss: Turn __nss_database_lookup into a compatibility symbol The function uses the internal service_user type, so it is not really usable from the outside of glibc. Rename the function to __nss_database_lookup2 for internal use, and change __nss_database_lookup to always indicate failure to the caller. __nss_next already was a compatibility symbol. The new implementation always fails and no longer calls __nss_next2. unscd, the alternative nscd implementation, does not use __nss_database_lookup, so it is not affected by this change.
Verified, glibc-2.28-64.el8 has __nss_database_lookup2 symbol and it has __nss_database_lookup as compat one.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:3513