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 2169786

Summary:	if global mdns is disabled then it cannot be turned on from NM per device
Product:	Red Hat Enterprise Linux 9	Reporter:	Vladimir Benes <vbenes>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED NOTABUG	QA Contact:	Frantisek Sumsal <fsumsal>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.2	CC:	bgalvani, systemd-maint-list, yuwatana
Target Milestone:	rc	Keywords:	Regression
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-02-15 13:44:58 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 Vladimir Benes 2023-02-14 17:05:14 UTC

Description of problem:
We have a test case in NMCI that started to fail on Feb 9 when system-resolved 252-4 landed in the compose. So now we can either enable mdns globally and disable it per link or we can disable it globally but then we are unable to turn it off per device. This is regression. 

Version-Release number of selected component (if applicable):
252-4

How reproducible:
always

Steps to Reproduce:
1. git clone https://gitlab.freedesktop.org/NetworkManager/NetworkManager-ci
2. cd NetworkManager-ci
3. ./test_run.sh dns_resolved_add_mdns

Actual results:

    @rhbz2015460
    @ver+=1.12
    @dns_systemd_resolved
    @dns_resolved_add_mdns
    Scenario: NM - dns - mdns
    * Add "ethernet" connection named "con_mdns" for device "eth2" with options "autoconnect no"
    * Bring "up" connection "con_mdns"
    Then "no" is visible with command "resolvectl mdns eth2"
    * Execute "nmcli connection modify con_mdns connection.mdns yes"
    * Bring "up" connection "con_mdns"
    Then "yes" is visible with command "resolvectl mdns eth2"

The last step is not working anymore

Expected results:
The last step should be working again

Additional info: