Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-17972

Hostname is not configured during ABI install from ACM with LACP bond configured using NMstate

XMLWordPrintable

    • None
    • None
    • ZStream
    • 1
    • rhel-sst-network-management
    • ssg_networking
    • 2
    • Hide
      Customer Jira ID Case ID Status Details
      Dell Technologies RHEL-17972 RHEL-17972 This issue involves the hostname not being correctly configured during an Agent-Based Installation with LACP bond configured using Nmstate on OpenShift 4.12.44. This results in nodes defaulting to "localhost.localdomain". Initial investigations revealed that NetworkManager fails to resolve the hostname due to delays caused by the STP forwarding timeout on the switch and this prevents immediate network connectivity.
      The current status is that the root cause has been identified and a workaround involves disabling STP or adjusting the switch settings to reduce the forwarding timeout. A MR is available upstream and is currently under review. 
      [2024-08-21] The MR is merged upstream and the fix will be available in the next NetworkManager build. The next step will be to backport the fix into RHEL-9.2 to be consumed by OpenShift. 
      Show
      Customer Jira ID Case ID Status Details Dell Technologies RHEL-17972 RHEL-17972 This issue involves the hostname not being correctly configured during an Agent-Based Installation with LACP bond configured using Nmstate on OpenShift 4.12.44. This results in nodes defaulting to "localhost.localdomain". Initial investigations revealed that NetworkManager fails to resolve the hostname due to delays caused by the STP forwarding timeout on the switch and this prevents immediate network connectivity. The current status is that the root cause has been identified and a workaround involves disabling STP or adjusting the switch settings to reduce the forwarding timeout. A MR is available upstream and is currently under review.  [2024-08-21] The MR is merged upstream and the fix will be available in the next NetworkManager build. The next step will be to backport the fix into RHEL-9.2 to be consumed by OpenShift. 
    • False
    • Hide

      None

      Show
      None
    • None
    • NMT - RHEL-9.5 DTM 24
    • Approved Blocker
    • Hide

      Given an OpenShift 4.12.44 platform installed on bare metal via ACM using assisted services and an NMState configuration for networking,

      When configuring a network interface as an LACP bond and utilizing a static IP configuration,

      Then the hostname assigned to the node during the installation process should be set according to the provided configuration and the node should not default to "localhost.localdomain" as the hostname upon booting up.

      Definition of Done:

      • The implementation meets the acceptance criteria
      • Unit test and integration test are written and pass
      • The fix is part of a downstream build attached to an errata
      • The fix is backported into rhel-9.2
         
      Show
      Given an OpenShift 4.12.44 platform installed on bare metal via ACM using assisted services and an NMState configuration for networking, When configuring a network interface as an LACP bond and utilizing a static IP configuration, Then the hostname assigned to the node during the installation process should be set according to the provided configuration and the node should not default to "localhost.localdomain" as the hostname upon booting up. Definition of Done: The implementation meets the acceptance criteria Unit test and integration test are written and pass The fix is part of a downstream build attached to an errata The fix is backported into rhel-9.2  
    • Pass
    • None
    • None

      What were you trying to do that didn't work?

      Platform:

      • OpenShift 4.12.44 on baremetal ( installation via ACM using assisted services)
      • Connected environment
      • Agent based installation with an NMState config for networking
      • Static IP config for a bond network interface
         
        Problem:
        While using LCAP the hostname is not taken by the nodes. Without LCAP they have tested and it works.

        Please provide the package NVR for which bug is seen:

        How reproducible:

        Steps to reproduce

      1.  Generate discovery iso with network config (LCAP bond)
      2. boot up the ISO
      3. node comes with localhost.localdomain

      Expected results

      Hostname should be assigned to the node once it is booted up.

      Actual results

      Node comes up as localhost.

              ihuguet@redhat.com Inigo Huguet
              rhn-support-chdeshpa Chinmay Deshpande
              Gris Ge Gris Ge
              Vladimir Benes Vladimir Benes
              Votes:
              1 Vote for this issue
              Watchers:
              16 Start watching this issue

                Created:
                Updated:
                Resolved: