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 1331870 - Looks like /etc/updatedb.conf does have a PRUNEFS variable updated with fuse.glusterfs
Summary: Looks like /etc/updatedb.conf does have a PRUNEFS variable updated with fuse....
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: mlocate
Version: 7.1
Hardware: All
OS: Linux
high
medium
Target Milestone: pre-dev-freeze
: 7.5
Assignee: Michal Sekletar
QA Contact: Karel Srot
URL:
Whiteboard:
Depends On:
Blocks: 1465901 1469361
TreeView+ depends on / blocked
 
Reported: 2016-04-29 21:03 UTC by Peter Portante
Modified: 2018-04-10 18:45 UTC (History)
6 users (show)

Fixed In Version: mlocate-0.26-8.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 18:45:34 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 762270 0 low CLOSED disable glusterfs mount from updatedb.conf 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1331944 0 unspecified CLOSED Add fuse.glusterfs to PRUNEFS in /etc/updatedb.conf 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2018:1004 0 None None None 2018-04-10 18:45:58 UTC

Internal Links: 762270 1331944

Description Peter Portante 2016-04-29 21:03:59 UTC 
Latest install of 3.1.2 did not seem to update /etc/updatedb.conf with the fuse.glusterfs exception.

See old BZ on this topic: https://bugzilla.redhat.com/show_bug.cgi?id=762270
Comment 2 Niels de Vos 2016-04-30 11:38:57 UTC 
Just like it is done for other filesystems, I prefer to see fuse.glusterfs added to the default PRUNEFS variable in the updatedb.conf from the mlocate package.

Could you move this bug to the RHEL version that you are interested in, and maybe clone it for others?

Bug 1331944 has been filed for Fedora, the distributions default updatedb.conf file is located here:

  http://pkgs.fedoraproject.org/cgit/rpms/mlocate.git/log/updatedb.conf
Comment 3 Peter Portante 2016-05-24 02:42:57 UTC 
Seems buggy to pass this to a central package.  Why can't GlusterFS update the configuration to make sure it is good for their users?  Especially in our products?
Comment 4 Niels de Vos 2016-07-05 10:13:36 UTC 
Our products include mlocate. Part of the productization is integrating with other components. Gluster should try hard not modify configuration files that other packages ship, and are not intended for automated modifications. If mlocate would offer a directory where Gluster can drop-in a config file, things would be different. We do not know how an administration modifies existing configuration files, and breaking that is bad behaviour.

Would you be opposed to it when I move this bug to RHEL/mlocate as suggested in comment #2?
Comment 5 Peter Portante 2016-07-06 01:42:14 UTC 
So /etc/updatedb.conf is supposed to be updated to add file systems and file system types that should not be considered, right?  What marks a file as not intended for automatic update?

It would be nice to have mlocate read a directory of config files to build up its notion of state.  But since we don't have that, wouldn't it be our place to make our product take this on until either upstream handles it properly?

This bug nearly took out my system from service by consuming the system disk.  That did not happen until Gluster was installed.  So, it seems like GlusterFS as a product should own this until some other part of the system does.

I will not oppose moving this to RHEL/mlocate, as I don't think that is my place.  It would nice to see that we can own the problems sufficiently to make sure they are solved for customers before handing them off to another team.
Comment 6 Niels de Vos 2016-07-07 11:37:59 UTC 
Moving this to RHEL/mlocate.

Because of this description, I think that a "high" priority is in order:

> This bug nearly took out my system from service by consuming the system
> disk.  That did not happen until Gluster was installed.  So, it seems like
> GlusterFS as a product should own this until some other part of the system
> does.

It would be an ugly workaround to try and modify a configuration file through some Gluster related scripts. There is no guarantee that the configuration file is available during the installation of the glusterfs-fuse package, mlocate can get installed afterwards. We would only be addressing one option, and may require more workarounds to address other cases.

Adding "fuse.glusterfs" to the PRUNFE variable in /etc/updatedb.conf that comes with mlocate is the best approach IMHO.
Comment 16 errata-xmlrpc 2018-04-10 18:45:34 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, 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/RHBA-2018:1004
Note You need to log in before you can comment on or make changes to this bug.