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 2186178

Summary: failures when DNS is set to auto with DHCP and there is a static DNS search string defined [rhel-8.8.0.z]
Product: Red Hat Enterprise Linux 8 Reporter: RHEL Program Management Team <pgm-rhel-tools>
Component: nmstateAssignee: Gris Ge <fge>
Status: CLOSED ERRATA QA Contact: Mingyu Shi <mshi>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.8CC: ferferna, fge, jiji, jishi, mifiedle, network-qe, sfaye, till, zzhao
Target Milestone: rcKeywords: Triaged, ZStream
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: nmstate-1.4.4-1.el8_8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2174710 Environment:
Last Closed: 2023-05-16 10:01:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2174710    
Bug Blocks:    
Attachments:
Description Flags
verified.log none

Comment 4 Mingyu Shi 2023-04-28 07:43:46 UTC
Created attachment 1960689 [details]
verified.log

Verified with:
nmstate-1.4.4-1.el8_8.x86_64
nispor-1.2.10-1.el8.x86_64
NetworkManager-1.40.16-1.el8.x86_64
DISTRO=RHEL-8.8.0-20230424.39

But for the 2nd issue, if ipv4 and ipv6 are both enabled(and all options set to auto), seems nmstate always writes the dns-search itmes to `ipv6.dns-search`:

[11:40:11@kvm-01-guest12 ~]0# diff before after
45c45
< ipv4.dns-search:                        qetest.org
---
> ipv4.dns-search:                        --
72c72
< ipv6.dns-search:                        --
---
> ipv6.dns-search:                        example.com,example.org

In `nmstatectl show`, the manual configured dns-search are not in `running`
[15:39:02@kvm-01-guest14 ~]0# nms show | head -20
---
dns-resolver:
  config:
    search:
    - example.com
    - example.org
    server: []
  running:
    search:
    - lab.eng.brq2.redhat.com
    - brq2.redhat.com
    - redhat.com
    server:
    - 10.45.248.15
    - 10.38.5.26
route-rules:
  config: []
routes:
  config: []
  running:

Comment 8 errata-xmlrpc 2023-05-16 10:01:31 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (nmstate bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:3092