Description of problem:
While scaling a 300 node cluster up to 1000 projects and 4000 running pods, the following node Error level message popped a few times in the log on the master. I need to check other nodes to see if they hit it, too.
Feb 7 22:56:58 192 atomic-openshift-node: E0207 22:56:58.045551 3115 proxier.go:755] conntrack return with error: Error looking for path of conntrack: exec: "conntrack": executable file not found in $PATH
Feb 7 22:56:58 192 atomic-openshift-node: E0207 22:56:58.045600 3115 proxier.go:755] conntrack return with error: Error looking for path of conntrack: exec: "conntrack": executable file not found in $PATH
Version-Release number of selected component (if applicable): 126.96.36.199
How reproducible: Unknown, saw a few instances during this test and will investigate other node logs
Expected: No Error or Fatal messages.
This cluster was installed with the latest (as of 7 Feb) master branch of openshift-ansible/playbooks/byo/config.yml
We need to make sure that the libnetfilter_conntrack RPM is installed on any node running openshift-node.
/usr/sbin/conntrack is provided by conntrack-tools need to ensure that's installed on all nodes.
Including verifying availability on atomic host and/or the containerized node image. Currently libnetfilter_conntrack is required there but not conntrack-tools
change for the container version:
not containerized version:
Verified this bug with openshift-ansible-3.5.13-1.git.0.562e91d.el7.noarch, and PASS.
For rpm install,the following step is shown in node install.
TASK [openshift_node : Install conntrack-tools package] ************************
After installation, check rpm package.
# rpm -q conntrack-tools
For containerized install:
# docker run --rm -ti --entrypoint rpm openshift3/node:v188.8.131.52 -q conntrack-tools
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.