Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2211820

Summary: network system role internal error if global-dns option set
Product: Red Hat Enterprise Linux 9 Reporter: Marko Myllynen <myllynen>
Component: rhel-system-rolesAssignee: Network Management Team <nm-team>
Status: CLOSED MIGRATED QA Contact: CS System Management SST QE <rhel-cs-system-management-subsystem-qe>
Severity: high Docs Contact:
Priority: unspecified    
Version: 9.2CC: rmeggins, sfaye, spetrosi
Target Milestone: rcKeywords: MigratedToJIRA, Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: role:network
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-12 10:03:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Marko Myllynen 2023-06-02 06:51:18 UTC
Description of problem:
With global-dns option set on RHEL 9.2

# cat /etc/NetworkManager/conf.d/90-dns-servers.conf
[global-dns]
options=no-aaaa

a playbook using the network system role with


    network_state:
      dns-resolver:
        config:
          server:
            - 192.168.122.1
      interfaces:
        - name: net0
          type: ethernet
          state: up
          ipv4:
            enabled: true
            auto-dns: false
          ipv6:
            enabled: false

fails with internal error:

...
        Traceback (most recent call last):                                                                                                                                                                                                    
          File "<stdin>", line 107, in <module>                                                                                                                                                                                               
          File "<stdin>", line 99, in _ansiballz_main                                                                                                                                                                                         
          File "<stdin>", line 47, in invoke_module                                                                                                                                                                                           
          File "/usr/lib64/python3.9/runpy.py", line 225, in run_module                                                                                                                                                                       
            return _run_module_code(code, init_globals, run_name, mod_spec)                                                                                                                                                                   
          File "/usr/lib64/python3.9/runpy.py", line 97, in _run_module_code                                                                                                                                                                  
            _run_code(code, mod_globals, init_globals,                                                                                                                                                                                        
          File "/usr/lib64/python3.9/runpy.py", line 87, in _run_code                                                                                                                                                                         
            exec(code, run_globals)                                                                                                                                                                                                           
          File "/tmp/ansible_redhat.rhel_system_roles.network_state_payload_8fppobvb/ansible_redhat.rhel_system_roles.network_state_payload.zip/ansible_collections/redhat/rhel_system_roles/plugins/modules/network_state.py", line 83, in <module>
          File "/tmp/ansible_redhat.rhel_system_roles.network_state_payload_8fppobvb/ansible_redhat.rhel_system_roles.network_state_payload.zip/ansible_collections/redhat/rhel_system_roles/plugins/modules/network_state.py", line 79, in main
          File "/tmp/ansible_redhat.rhel_system_roles.network_state_payload_8fppobvb/ansible_redhat.rhel_system_roles.network_state_payload.zip/ansible_collections/redhat/rhel_system_roles/plugins/modules/network_state.py", line 75, in run_module
          File "/tmp/ansible_redhat.rhel_system_roles.network_state_payload_8fppobvb/ansible_redhat.rhel_system_roles.network_state_payload.zip/ansible_collections/redhat/rhel_system_roles/plugins/modules/network_state.py", line 46, in run
          File "/usr/lib/python3.9/site-packages/libnmstate/netapplier.py", line 29, in apply
            return apply_net_state(
          File "/usr/lib/python3.9/site-packages/libnmstate/clib_wrapper.py", line 127, in apply_net_state
            raise map_error(err_kind, err_msg)
        libnmstate.error.NmstateInternalError: Bug: zbus fdo error Unknown: Unknown
        debug3: mux_client_read_packet: read header failed: Broken pipe
        debug2: Received exit status from master 1
    module_stdout: ''
    msg: |-
        MODULE FAILURE
        See stdout/stderr for the exact error
    rc: 1
...

Commenting out the global-dns option, restarting NM, and trying again allows the playbook to complete as expected.

Version-Release number of selected component (if applicable):
rhel-system-roles-1.21.1-1.el9_2.noarch

Comment 2 RHEL Program Management 2023-09-12 09:58:15 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 3 RHEL Program Management 2023-09-12 10:03:30 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.