![]() The OpenShift installer modifies /etc/resolv.conf then tests the new resolver configuration, however, there was no mechanism to reload resolv.conf in our reuseable interpreter. https://github.com/openshift/openshift-ansible/blob/release-3.9/roles/openshift_web_console/tasks/install.yml#L137 This inserts an explicit call to res_init() for every new style invocation, with an approximate cost of ~1usec on Linux since glibc verifies resolv.conf has changed before reloading it. There is little to be done for users of the thread-safe resolver APIs, their state is hidden from us. If bugs like that manifest, whack-a-mole style 'del sys.modules[thatmod]' patches may suffice. |
||
---|---|---|
.. | ||
all.yml | ||
resolv_conf.yml |