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

[RHEL10] NetworkManager doesn't start the dnsconfd service when needed

XMLWordPrintable

    • NetworkManager-1.52.0-1.el10_0
    • No
    • Moderate
    • rhel-sst-network-management
    • ssg_networking
    • 28
    • 29
    • 3
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • Approved Blocker
    • Hide

      Given NetworkManager is configured to use dnsconfd as its DNS backend,

      When NetworkManager detects that the dnsconfd service is not running,

      Then NetworkManager should automatically start the dnsconfd service before attempting to send DNS updates.

      Definition of Done:

      • The implementation meets the acceptance criteria
      • Integration tests are written and pass 
      • The code is part of a downstream build attached to an errata
      Show
      Given NetworkManager is configured to use dnsconfd as its DNS backend, When NetworkManager detects that the dnsconfd service is not running, Then NetworkManager should automatically start the dnsconfd service before attempting to send DNS updates. Definition of Done: The implementation meets the acceptance criteria Integration tests are written and pass  The code is part of a downstream build attached to an errata
    • Pass
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • None

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

      When NetworkManager is configured to use dnsconfd as DNS backend and the dnsconfd service is not running, NM doesn't try to start it. Instead it doesn't send any update and the result it that the system cannot resolve names.

      The upstream fix for this is: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/2144

      What is the impact of this issue to you?

      This prevents the usage of encrypted DNS during installation and early boot.

      Please provide the package NVR for which the bug is seen:

      NetworkManager-1.51.90-2.el10

      How reproducible is this bug?:

      Always

       

            [RHEL-80307] [RHEL10] NetworkManager doesn't start the dnsconfd service when needed

            Shelley Dunne added a comment -

            rhn-engineering-vbenes Hello, We are very close to the end of ITM 32 when all Errata need to be in REL_PREP, when you expect to get this bug to Release Pending?

            Shelley Dunne added a comment - rhn-engineering-vbenes Hello, We are very close to the end of ITM 32 when all Errata need to be in REL_PREP, when you expect to get this bug to Release Pending?

            RHEL Jira bot added a comment -

            The release blocker/exception task has completed successfully and your blocker/exception request has been set as Approved Blocker. Please plan/complete this work accordingly.

            RHEL Jira bot added a comment - The release blocker/exception task has completed successfully and your blocker/exception request has been set as Approved Blocker. Please plan/complete this work accordingly.

            RHEL Jira bot added a comment -

            No Permission: Tomáš Korbař Proposed this Blocker/Exception. They are not a member of the rhel-oversight or rhel-po Rover Groups.

            RHEL Jira bot added a comment - No Permission: Tomáš Korbař Proposed this Blocker/Exception. They are not a member of the rhel-oversight or rhel-po Rover Groups.

              rhn-engineering-vbenes Vladimir Benes
              bgalvani@redhat.com Beniamino Galvani
              Network Management Team Network Management Team
              Vladimir Benes Vladimir Benes
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: