-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.19
-
Important
-
None
-
1
-
Metal Platform 270
-
1
-
Rejected
-
False
-
-
-
Bug Fix
-
Done
This is a clone of issue OCPBUGS-55315. The following is the description of the original issue:
—
It seems that the hostname handling code in our downstream ironic-agent plugin is racy. The sequence of events as recovered from a CI job run:
- IPA starts and polls all hardware manager
- Our hardware managers detects the hostname, fixes it if needed and records in a variable
- IPA proceeds with its regular business, including inspection
- During inspection, a different hostname is returned from socket.gethostname, and it gets reported back to Ironic and thus BMO.
- During OS installation, our plugin configures Ignition with the earlier hostname, not the one reported in Inspection.
- This way, the Machine resource ends up with the later (correct) hostname, while the Node boots with an earlier hostname. They mismatch, and the Node does not get approved.
- clones
-
OCPBUGS-55364 Race condition when handling hostname in ironic-agent
-
- Closed
-
- depends on
-
OCPBUGS-55364 Race condition when handling hostname in ironic-agent
-
- Closed
-
- links to
-
RHBA-2025:4723 OpenShift Container Platform 4.17.z bug fix update