Bug 2050113

Summary:	unknown response: etnameinfo failed: Unknown error
Product:	[Fedora] Fedora	Reporter:	Nuno Dias <nuno.dias>
Component:	amanda	Assignee:	Jason Tibbitts <j>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	35	CC:	fedora, jridky, j, pcahyna, phracek, rvokal
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-02-08 09:36: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 Nuno Dias 2022-02-03 09:39:54 UTC

Description of problem:
Since the upgrade to Fedora 35 I have this error every time I try to use amanda

In the server I get this error when running amcheck

ERROR: xxx.xxx.xxx.xxx: unknown response: etnameinfo failed: Unknown error

In the client in the logs I have

amandad: getnameinfo failed: Unknown error

The server that is not Fedora 35, works with other machines

Version-Release number of selected component (if applicable):
amanda-3.5.1-32.fc35.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. Run amcheck and configure a client with Fedora 35
2.
3.

Actual results:
Fail

Expected results:
No Error

Additional info:
The name resolution works and I can resolve names.

Comment 1 Nuno Dias 2022-02-08 09:32:14 UTC

It seams the Server fails everytime with the same error, in all Fedora 35 clients
The Server is Fedora 34 and works with all flavours that are not Fedora 34

Comment 2 Nuno Dias 2022-02-08 09:36:58 UTC

Ok, the culprit was the systemd-resolved.service after restart the service amanda works again as expected.