Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1830204

Summary: Node hostname is set to pod name
Product: OpenShift Container Platform Reporter: Apurva Nisal <anisal>
Component: NodeAssignee: Peter Hunt <pehunt>
Status: CLOSED ERRATA QA Contact: Sunil Choudhary <schoudha>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.11.0CC: anisal, aos-bugs, jokerman, mpatel, pehunt
Target Milestone: ---   
Target Release: 3.11.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-08-26 22:44:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Apurva Nisal 2020-05-01 04:50:44 UTC 
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
--------------------------------------------------------------
Comment 1 Peter Hunt 2020-05-14 15:56:11 UTC 
what is the output of `cat /proc/sys/kernel/pid_max`
Comment 3 Peter Hunt 2020-05-15 17:22:07 UTC 
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?
Comment 23 errata-xmlrpc 2020-08-26 22:44:37 UTC 
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