Bug 1882477

Summary:	nss-mdns resolving names very slowly
Product:	[Fedora] Fedora	Reporter:	Matt Rose <mattrose>
Component:	nss-mdns	Assignee:	Adam Goode <adam>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	32	CC:	adam, lpoetter
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-05-25 16:47:39 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 Matt Rose 2020-09-24 16:38:46 UTC

Description of problem:

Using nss-mdns straight out of the box on F32, it takes dozens of seconds 
for mdns hostsnames to resolve, for example:

[mattrose@sorrento terminator]$ time avahi-resolve -n rome.local
rome.local	10.0.1.8

real	0m0.009s
user	0m0.005s
sys	0m0.002s

[mattrose@sorrento terminator]$ time getent hosts rome.local
10.0.1.8        rome.local

real	0m48.119s
user	0m0.000s
sys	0m0.004s


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

nss-mdns-0.14.1-7.fc32.x86_64

How reproducible:

As far as I can tell, every time.  Somebody else on the #fedora channel was able to reproduce with a stock F32 install


Steps to Reproduce:
1.  Get on a network that has devices that advertise their hostnames over multicast.
2.  Try to get the address of the host purely through avahi
3.  Try to get the address of the host through NSS


Actual results:

As shown, avahi resolves the hostname in 9 milliseconds
nss takes as long as 48 *seconds*

Expected results:

nss should resolve the hostname in roughly the same time as avahi-resolve.


Additional info:

Comment 1 Fedora Program Management 2021-04-29 16:38:50 UTC

This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Ben Cotton 2021-05-25 16:47:39 UTC

Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.