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

Hostname set to FQDN when set through RDNS lookup

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • NetworkManager-1.54.0-1.el10
    • No
    • Moderate
    • 1
    • rhel-net-mgmt
    • 2
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • NMT Sprint until 2025-07-31
    • Hide

      Definition of Done:

      Please mark each item below with ( / ) if completed or ( x ) if incomplete:

      The acceptance criteria defined below are met.

      Given a RHEL 10 host managed by NetworkManager with reverse DNS returning a FQDN longer than 64 characters,

      When NetworkManager performs RDNS and attempts to set the system hostname,

      Then NetworkManager must extract the short hostname from the RDNS result so that system can acquire valid system hostnames from RDNS even when FQDNs are long.

      Code changes are included in a downstream build attached to an errata.

      All required testing (manual and/or automated) passes successfully.

      ( ) Related documentation updates (if applicable) have been completed.

      ( ) All necessary backports to the related RHEL streams (linked as 'relates' in this issue) have been completed and verified.

      Show
      Definition of Done: Please mark each item below with ( / ) if completed or ( x ) if incomplete: The acceptance criteria defined below are met. Given a RHEL 10 host managed by NetworkManager with reverse DNS returning a FQDN longer than 64 characters, When NetworkManager performs RDNS and attempts to set the system hostname, Then NetworkManager must extract the short hostname from the RDNS result so that system can acquire valid system hostnames from RDNS even when FQDNs are long. Code changes are included in a downstream build attached to an errata. All required testing (manual and/or automated) passes successfully. ( ) Related documentation updates (if applicable) have been completed. ( ) All necessary backports to the related RHEL streams (linked as 'relates' in this issue) have been completed and verified.
    • Pass
    • Automated
    • Unspecified
    • Unspecified
    • Unspecified
    • None

      Hi team,

      we notice that network manager tries to set the FDQN of the machine as hostname when looking for it using reverse DNS. This operation fails often because the FQDN is usually longer than 64 characters (see https://issues.redhat.com/browse/MGMT-18893).

      For example, in case of "javipolo-cp-3.private.openshiftvcn.oraclevcn.com", the hostname should only be "javipolo-cp-3", and the domain just be in the search part.

      I wanted to check with you if this behavior of NetworkManger is expected, and if we can find a workaround.

      Thank you

              bgalvani@redhat.com Beniamino Galvani
              agentil@redhat.com Adrien Gentil
              Network Management Team Network Management Team
              Vladimir Benes Vladimir Benes
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated: