-
Bug
-
Resolution: Done-Errata
-
Major
-
4.19
-
Important
-
None
-
0
-
Metal Platform 271
-
1
-
Rejected
-
False
-
-
The readability of the deployment ramdisk logs in the metal3-ramdisk-logs container of the metal3 pod has been improved. Previously, all files from the ramdisk were written to the output without a break. Now they have a clear header.
-
Bug Fix
-
In Progress
This is a clone of issue OCPBUGS-55743. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-55381. The following is the description of the original issue:
—
Description of problem:
Ramdisk logs are created by dumping an entire tarball to stdout. As a result, file separators are hard to detect, and sometimes they end up at the end of a random line instead of a new line, like this (ip_addr is the file name):
2025-04-25T12:05:44.727687118Z 7356cfea-1e0e-4238-9623-007fd58be6cf_openshift-machine-api~ostest-worker-2_11ff0b22-3746-425c-951f-fb482b135dc1_cleaning_2025-04-25-12-05-44.tar.gz: [ Â Â 1.390910] systemd[1]: Queued start job for default target Initrd De-rw-r--r-- 0/0 Â Â Â Â Â Â 1096 2025-04-25 12:05 ip_addr
Let us try to at least make it clear where one file ends and the next begins.
- clones
-
OCPBUGS-55743 Ramdisk logs are unreadable and unparseable
-
- Verified
-
- is blocked by
-
OCPBUGS-55743 Ramdisk logs are unreadable and unparseable
-
- Verified
-
- links to
-
RHBA-2025:7863 OpenShift Container Platform 4.18.14 bug fix update