Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1990589

Summary: chrony FTBFS on a fresh RHEL-9 Beta nightly: 099-scfilter -> 007-cmdmon -> FAIL
Product: Red Hat Enterprise Linux 9 Reporter: Alexander Sosedkin <asosedki>
Component: chronyAssignee: Miroslav Lichvar <mlichvar>
Status: CLOSED CURRENTRELEASE QA Contact: Ondrej Mejzlik <omejzlik>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.0CC: omejzlik
Target Milestone: betaKeywords: EasyFix, Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: chrony-4.1-3.el9 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-12-07 21:44:43 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 Alexander Sosedkin 2021-08-05 16:45:23 UTC
Description of problem: chrony upstream testsuite fails on RHEL-9.0.0-20210804.6 nightly
Version-Release number of selected component (if applicable): chrony-4.1-1.el9
How reproducible: reliably
Steps to Reproduce: try to recompile chrony
Actual results:
   099-scfilter   Testing system call filter in non-destructive tests:
     level -1:
       001-minimal                                                 OK
       002-extended                                                OK
       003-memlock                                                 OK
       004-priority                                                OK
       006-privdrop                                                OK
       007-cmdmon                                                  BAD
   FAIL
  --- 8< ---
   SUMMARY:
     TOTAL  16
     PASSED 9
     FAILED 1    (099-scfilter)
     SKIPPED 6   (100-clockupdate 101-rtc 102-hwtimestamp 103-refclock 104-systemdirs 199-scfilter)
Expected results: testsuite succeeds
Additional info:
    fails on RHEL-9.0.0-20210804.6 with BUILDROOT-9.0.0-20210804.5,
    passes on RHEL-9.0.0-20210728.4 with BUILDROOT-9.0.0-20210728.1

Comment 1 Alexander Sosedkin 2021-08-05 18:45:25 UTC
And, I suppose, now the same thing started happening when building chrony-4.1-1.fc34 on Fedora 34.

Comment 3 Miroslav Lichvar 2021-08-09 10:34:46 UTC
It seems this due to the glibc update. New system calls need to be allowed in the chrony seccomp filter.

https://git.tuxfamily.org/chrony/chrony.git/commit/?id=bbbd80bf03223f181d4abf5c8e5fe6136ab6129a