Bug 1313393

Summary:	Test suite failure: posix/tst-getaddrinfo5
Product:	[Fedora] Fedora	Reporter:	Carlos O'Donell <codonell>
Component:	glibc	Assignee:	glibc team <glibc-bugzilla>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	24	CC:	arjun.is, codonell, dj, fweimer, jakub, law, mfabian, pfrankli, siddhesh
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1313437 (view as bug list)		Environment:
Last Closed:	2017-07-27 12:03:56 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:
Bug Depends On:
Bug Blocks:	1313437

Description Carlos O'Donell 2016-03-01 14:21:05 UTC

On 32-bit armv7hl the posix/tst-getaddrinfo5 test failus with:

resolving "localhost." failed, skipping this hostname
resolving "www.gnu.org." failed, skipping this hostname

This is odd, but perhaps the builders have a restricted build environment.

We should investigate this and consider rewriting the test.

Comment 1 Carlos O'Donell 2016-03-01 14:21:59 UTC

Also seen on on x86_64.

Comment 2 Carlos O'Donell 2016-03-01 14:22:22 UTC

Also seeon on i686.

Comment 3 Florian Weimer 2016-03-01 14:26:51 UTC

This test should really fail everywhere.  If it does not, it means the builder has working DNS resolution and potentially more extensive Internet access, which is not what we want.

We can fix this test easily once we have the resolver harness integrated.

Comment 4 Carlos O'Donell 2016-03-01 15:29:34 UTC

(In reply to Florian Weimer from comment #3)
> This test should really fail everywhere.  If it does not, it means the
> builder has working DNS resolution and potentially more extensive Internet
> access, which is not what we want.
> 
> We can fix this test easily once we have the resolver harness integrated.

Agreed, we shouldn't be doing any testing that involves resolving names externally outside of the test framework.

Comment 5 Fedora End Of Life 2017-07-25 20:16:18 UTC

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 6 Florian Weimer 2017-07-27 12:03:56 UTC

Upstream will fix this eventually as part of more extensive container-based testing.