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

Missing NetworkManager logs for ironic-python-agent

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 3
    • None
    • None
    • None
    • None
    • Metal Platform 270, Metal Platform 271
    • 2
    • Done
    • Bug Fix
    • Hide
      * Before this update, during Ironic Python Agent (IPA) deployments, the RAM disk logs in the `metal3-ramdisk-logs` container did not include `NetworkManager` logs. The absence of `NetworkManager` logs hindered effective debugging, which affected network issue resolution. With this release, the existing RAM disk logs in the `metal3-ramdisk-logs` container of a metal3 pod include the entire journal from the host rather than just the `dmesg` and IPA logs. As result, IPA logs provide comprehensive `NetworkManager` data for improved debugging. (link:https://issues.redhat.com/browse/OCPBUGS-55350[OCPBUGS-55350])
      Show
      * Before this update, during Ironic Python Agent (IPA) deployments, the RAM disk logs in the `metal3-ramdisk-logs` container did not include `NetworkManager` logs. The absence of `NetworkManager` logs hindered effective debugging, which affected network issue resolution. With this release, the existing RAM disk logs in the `metal3-ramdisk-logs` container of a metal3 pod include the entire journal from the host rather than just the `dmesg` and IPA logs. As result, IPA logs provide comprehensive `NetworkManager` data for improved debugging. (link: https://issues.redhat.com/browse/OCPBUGS-55350 [ OCPBUGS-55350 ])
    • None
    • None
    • None
    • None

      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
              bnemec@redhat.com Benjamin Nemec
              None
              None
              Jad Haj Yahya Jad Haj Yahya
              None
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: