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 1978587 - filesystem-content sanity test fails
Summary: filesystem-content sanity test fails
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: filesystem
Version: 9.0
Hardware: All
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: ---
Assignee: Nobody
QA Contact: František Hrdina
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-02 08:56 UTC by František Hrdina
Modified: 2021-12-07 21:55 UTC (History)
2 users (show)

Fixed In Version: filesystem-3.14-8.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-12-07 21:52:33 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description František Hrdina 2021-07-02 08:56:20 UTC 
Description of problem:
Failing test /CoreOS/filesystem/Sanity/content 
There is a difference between outputs of
comm -13 ghostfiles /usr/share/filesystem/paths >by_file_noghost and rpm -ql --noghost filesystem | sort  filesystem

beaker job results:
https://beaker.engineering.redhat.com/recipes/10232556#task128302287


Version-Release number of selected component (if applicable):
filesystem.x86_64            3.14-6.el9
filesystem-content.x86_64    3.14-6.el9

How reproducible:
always

Steps to Reproduce:
1. run the test using 1minutetip or in the beaker on rhel9 (filesystem-content installed using buildroot)


Actual results:
both outputs are not the same

Expected results:
should be same

Additional info:

:: [ 03:12:51 ] :: [  ERROR   ] :: =====BEGIN FILE lists.diff=====
:: [ 03:12:51 ] :: [  ERROR   ] :: --- by_rpmdb_noghost	2021-07-02 03:12:41.456150375 -0400
:: [ 03:12:51 ] :: [  ERROR   ] :: +++ by_file_noghost	2021-07-02 03:12:41.593150375 -0400
:: [ 03:12:51 ] :: [  ERROR   ] :: @@ -1,4 +1,5 @@
:: [ 03:12:51 ] :: [  ERROR   ] ::  /
:: [ 03:12:51 ] :: [  ERROR   ] :: +/afs
:: [ 03:12:51 ] :: [  ERROR   ] ::  /bin
:: [ 03:12:51 ] :: [  ERROR   ] ::  /boot
:: [ 03:12:51 ] :: [  ERROR   ] ::  /dev
:: [ 03:12:51 ] :: [  ERROR   ] :: =====END FILE lists.diff=====
Comment 2 Pavel Zhukov 2021-07-07 09:52:17 UTC 
https://src.fedoraproject.org/rpms/filesystem/c/c5bdcc96b6acc3fe43f97ec018ee84de471f6db6?branch=rawhide
Comment 9 jsbillings 2021-07-21 18:03:48 UTC 
Is there a reason why the only solution is to remove the filesystem-afs subpackage?  We will rely on that for CentOS 9 Stream packages in the kmod SIG and the Storage SIG, which provide AFS packages.  

The Fedora package kafs-client relies on filesystem-afs, which we planned on just building in c9s.
Comment 10 Jeffrey Altman 2021-07-21 18:16:53 UTC 
/afs was approved for inclusion in any future FHS revision.

The filesystem-afs package provides the /afs directory which is the mount point used by AuriStorFS, OpenAFS and Linux in-tree afs (kafs) more than one of which can be installed on a rhel system at a time.  The packaging of filesystem-afs avoids a variety of installation, upgrade and removal issues when AuriStorFS, OpenAFS or kafs packages are present.

Please revert this change.
Comment 11 Pavel Zhukov 2021-07-22 05:55:32 UTC 
(In reply to Jeffrey Altman from comment #10)
> /afs was approved for inclusion in any future FHS revision.
> 
> The filesystem-afs package provides the /afs directory which is the mount
> point used by AuriStorFS, OpenAFS and Linux in-tree afs (kafs) more than one
> of which can be installed on a rhel system at a time.  The packaging of
> filesystem-afs avoids a variety of installation, upgrade and removal issues
> when AuriStorFS, OpenAFS or kafs packages are present.
> 
> Please revert this change.

Jeffrey, this change has nothing to do with -afs subpackage removal. It was not removed as the result of this change. It *never* existed in RHEL/C9S composes.
Comment 12 Jeffrey Altman 2021-07-27 16:52:19 UTC 
Pavel,

My apologies for the misunderstanding of the purpose of this change.   Thank you for the explanation.

Jeffrey Altman
Note You need to log in before you can comment on or make changes to this bug.