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

[4.12] coreos-installer output not available in the logs

XMLWordPrintable

    • Moderate
    • None
    • 1
    • Metal Platform 229, Metal Platform 230
    • 2
    • False
    • Hide

      None

      Show
      None
    • Hide
      For the {product-title} {product-version}, the `coreos-installer` command output is now passed to the `metal3-ramdisk-logs` container log file. This update fixes a debugging issue that occurred when you wrote images on the {product-title} web console that required `coreos-installer` output information.

      (link:https://issues.redhat.com/browse/OCPBUGS-5067[*OCPBUGS-5067*])
      Show
      For the {product-title} {product-version}, the `coreos-installer` command output is now passed to the `metal3-ramdisk-logs` container log file. This update fixes a debugging issue that occurred when you wrote images on the {product-title} web console that required `coreos-installer` output information. (link: https://issues.redhat.com/browse/OCPBUGS-5067 [* OCPBUGS-5067 *])
    • Done

      Description of problem:

      Since coreos-installer writes to stdout, its logs are not available for us.

      Version-Release number of selected component (if applicable):

       

      How reproducible:

       

      Steps to Reproduce:

      1.
2.
3.

      Actual results:

       

      Expected results:

       

      Additional info:

       

              rhn-engineering-dtantsur Dmitry Tantsur
              rhn-engineering-dtantsur Dmitry Tantsur
              Jad Haj Yahya Jad Haj Yahya
              Darragh Fitzmaurice Darragh Fitzmaurice
              Red Hat Employee
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: