Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-55381

Ramdisk logs are unreadable and unparseable

XMLWordPrintable

    • Important
    • None
    • 2
    • Metal Platform 270
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • 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

      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.

              rhn-engineering-dtantsur Dmitry Tantsur
              rhn-engineering-dtantsur Dmitry Tantsur
              Jad Haj Yahya Jad Haj Yahya
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: