Bug 1814158

Summary:	bind internal testsuite, random failure in autosign
Product:	Red Hat Enterprise Linux 8	Reporter:	Petr Sklenar <psklenar>
Component:	bind	Assignee:	Petr Menšík <pemensik>
Status:	CLOSED ERRATA	QA Contact:	Petr Sklenar <psklenar>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.0	CC:	pemensik
Target Milestone:	rc	Keywords:	TestOnly, Triaged
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-04 01:50:44 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:	1818785
Bug Blocks:	1817044, 1825061

Description Petr Sklenar 2020-03-17 09:01:00 UTC

Description of problem:
bind internal testsuite, random failure in autosign.
Try to schedule internal testsuite many times.

Version-Release number of selected component (if applicable):
9.11.14
not arch specific, x86_64 shows the same as the rest of arch

How reproducible:
random, 30% of many run

Steps to Reproduce:
1. /usr/bin/bkr workflow-tomorrow --task=/CoreOS/bind/Sanity/Run-internal-BIND-test-suite --distro=rhel8.2 --repeat=10 --init-task /distribution/install/rhel8-buildroot


Actual results:
https://beaker.engineering.redhat.com/jobs/4127416

Expected results:
internal testsuite pass

Additional info:
pemensik info:
 Version 9.11.14 - checkjitter() is the cause. Random failure is possible it's maybe fixable in rhel83.

its not a regression as checkjitter was changes many times.

Comment 4 Petr Menšík 2020-06-04 19:36:15 UTC

It seems occasional failures in autosign test might be okay. It generates random jitter, which may generate from time to time more records into the same day than test accepts.

Comment 12 errata-xmlrpc 2020-11-04 01:50:44 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, bug fix, and enhancement 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-2020:4500