Description of problem: Node hostname is set to pod name. This issue occurs on nodes with node-group="node-config-compute-crio". Version-Release number of selected component (if applicable): crio version 1.11.14-2.rhaos3.11.gitd56660e.el7 atomic-openshift-node-3.11.104-1.git.0.95ffd35.el7.x86_64 How reproducible: Semi-random Steps to Reproduce: Using crio version 1.11.14-2.rhaos3.11.gitd56660e.el7 on nodes Actual results: # hostnamectl | grep -i trans Transient hostname: <PODNAME> Additional info: ------------------------------------------------------------- Title: Node hostname is set to pod name Link: https://github.com/cri-o/cri-o/issues/2983 --------------------------------------------------------------
what is the output of `cat /proc/sys/kernel/pid_max`
a mitigation for this problem is setting pid_max to the maximum allowed value. I'm assuming you're running 64 bit, so that's 2^22. A more complete solution will be invasive and difficult for such an old version of cri-o. (for reference, the capability to fully mitigate this is in cri-o 1.16, and openshift 3.11 has cri-o 1.11). I'd rather customers take the (comparatively much safer) work around unless absolutely necessary. Can you please update pid_max to the max?
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 (OpenShift Container Platform 3.11.272 bug fix and enhancement update), 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/RHBA-2020:3245