Bug 1675235

Summary: knot: FTBFS in Fedora rawhide/f30
Product: [Fedora] Fedora Reporter: Fedora Release Engineering <releng>
Component: knotAssignee: Paul Wouters <pwouters>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: jv+fedora, petr.spacek, pwouters, tomas.krizek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: knot-2.7.6-3.fc30 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-28 15:12:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1674516    
Description Flags
state.log none

Description Fedora Release Engineering 2019-02-11 20:38:24 UTC
knot failed to build from source in Fedora rawhide/f30


For details on the mass rebuild see:

Please fix knot at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
knot will be orphaned. Before branching of Fedora 31,
knot will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:

Comment 1 Fedora Release Engineering 2019-02-11 20:38:26 UTC
Created attachment 1530816 [details]

file build.log too big, will only attach last 1024 bytes

Comment 2 Fedora Release Engineering 2019-02-11 20:38:28 UTC
Created attachment 1530817 [details]

file root.log too big, will only attach last 1024 bytes

Comment 3 Fedora Release Engineering 2019-02-11 20:38:29 UTC
Created attachment 1530818 [details]

Comment 4 Tomas Krizek 2019-02-12 09:09:02 UTC
We've been investigating this failure and the specific test that fails is:

contrib/test_net: not ok 68 - UDP, send on defined address

We haven't identified any issue with the test itself in upstream. The test passes on x86_64 and seems to fail mainly on aarch64. Unfortunately, we don't have access to any aarch64 machine, so we have no easy way to debug it.

Since the test didn't change since last release, we suspect it might have started to fail due to some dependency.

Comment 5 Tomas Krizek 2019-02-28 15:12:20 UTC
Turns out the test isn't needed for Knot DNS, so I've disabled it.

Interestingly, the last time this particular test has passed successfully on all arches in F30 was right before the rebase to kernel 5.0.