Bug 1980916

Summary:	dns_tkey_gssnegotiate: TKEY is unacceptable" during ipa-client-install
Product:	Red Hat Enterprise Linux 8	Reporter:	Petr Menšík <pemensik>
Component:	bind	Assignee:	Petr Menšík <pemensik>
Status:	CLOSED ERRATA	QA Contact:	Petr Sklenar <psklenar>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	8.6	CC:	aegorenk, mescanfe, psklenar, rakkumar, rhel-cs-infra-services-qe
Target Milestone:	beta	Keywords:	Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	bind-9.11.26-6.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1980757	Environment:
Last Closed:	2021-11-09 19:35:15 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:	1980757
Bug Blocks:

Comment 2 Petr Menšík 2021-07-16 12:15:21 UTC

This issue is tricky to test. For reliable test we need two nsupdate runs to choose the same srand() value to initialize random numbers generator. It would happen when VM or container would have nsupdate as part of boot process and boots machines started at the same time, passing the same pid and time into srand() initialization. The outcome is therefore two same "random" key identifiers. If it attempts to use tkey with the same random value, only the first would succeed. The second would fail, because random key would still exist.

It would help for reliable reproduction to delay TKEY reply from BIND to nsupdate a bit, so the two sessions are active at the same time. If first is finished before the second start, it should work well even with the same random identifier.

Comment 11 errata-xmlrpc 2021-11-09 19:35:15 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 (Moderate: bind security and bug fix 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/RHSA-2021:4384