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

Missing NetworkManager logs for ironic-python-agent

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 0
    • None
    • None
    • None
    • None
    • Metal Platform 271
    • 1
    • Done
    • Bug Fix
    • Hide
      * Previously, NetworkManager logs from the Ironic Python Agent (IPA) were not included in the ramdisk logs; instead only `dmesg` logs were included in the ramdisk logs. With this release, the ramdisk logs that exist in the `metal3-ramdisk-logs` container of a metal3 pod now contain the entire journal from the host instead of just `dmesg` logs and IPA. (link:https://issues.redhat.com/browse/OCPBUGS-56042[OCPBUGS-56042])
      Show
      * Previously, NetworkManager logs from the Ironic Python Agent (IPA) were not included in the ramdisk logs; instead only `dmesg` logs were included in the ramdisk logs. With this release, the ramdisk logs that exist in the `metal3-ramdisk-logs` container of a metal3 pod now contain the entire journal from the host instead of just `dmesg` logs and IPA. (link: https://issues.redhat.com/browse/OCPBUGS-56042 [ OCPBUGS-56042 ])
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-55350. The following is the description of the original issue:
      —
      Description of problem:

      The ramdisk logs we get from IPA only include the output of dmesg, which by default does not include most NetworkManager log messages. This makes it difficult to debug problems like https://issues.redhat.com/browse/OCPBUGS-55315 and https://issues.redhat.com/browse/OCPBUGS-30974 that seem to be caused by network config happening at the IPA stage of deployment. These could be configuration problems in the environment, but there's no way to tell.

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

       One of the bugs listed above is for 4.18, but this likely applies to all releases.

      How reproducible:

          Always, although the bugs in question are intermittent. NetworkManager logs are never included in the ramdisk logs though.

      Steps to Reproduce:

          1. Deploy a cluster
    2. Look at the ramdisk logs from metal3.
    3.

      Actual results:

          Very few NetworkManager logs

      Expected results:

          All NetworkManager logs

      Additional info:

              rhn-engineering-dtantsur Dmitry Tantsur
              openshift-crt-jira-prow OpenShift Prow Bot
              None
              None
              Jad Haj Yahya Jad Haj Yahya
              None
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: