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.
DescriptionMichal Domonkos
2018-11-01 14:24:00 UTC
Description of problem:
When running "yum clean plugins" or "yum clean all", the product-id metadata files are not removed from the yum cache.
I'm not sure if this is by design or just hasn't been considered yet. However, I think the product-id plugin should define the clean hook and remove the files it fetches.
Reason I'm filing this:
Starting with RHEL-7.6, after "yum clean all" does its usual thing, it recurses into the cachedir and looks for any uncleaned data. If some is found, the message "Other repos take up ... of disk space" is printed, to inform the user of the fact that manual clean-up might be necessary.
The message has been added because people would incorrectly think that "yum clean all" would really purge everything. Whereas in reality, it only affects the enabled repos and the current releasever/arch combination (so-called "operational cachedir"). Had they ever disabled or removed a repo or fetched some repos with a different --releasever, they would have been surprised why a "yum clean all" still leaves files behind in the cachedir.
Now, since the productid files are never removed (not even from the operational cachedir), yum would always detect these and show the "Other repos take up..." message. That defeats the purpose of the hint as it's basically a false positive.
In case there's an actual reason for keeping those productid files around even after a clean-up, I guess yum could specifically ignore these in the detection routine. If you think so, please reassing this BZ to yum.
Version-Release number of selected component (if applicable):
yum-3.4.3-161.el7.noarch
How reproducible:
100%
Steps to Reproduce:
1. Subscribe your system to CDN
2. Make sure the default CDN repos are enabled
3. # yum makecache
4. # yum clean all
Actual results:
Loaded plugins: product-id, search-disabled-repos, subscription-manager
Cleaning repos: rhel-7-server-rpms
Other repos take up 3.7 k of disk space (use --verbose for details)
Expected results:
Loaded plugins: product-id, search-disabled-repos, subscription-manager
Cleaning repos: rhel-7-server-rpms
Additional information:
# yum clean all --verbose
[...]
Cleaning repos: rhel-7-server-rpms
Operating on /var/cache/yum/x86_64/7Server (see CLEAN OPTIONS in yum(8) for details)
Disk usage of /var/cache/yum/*/* after cleanup:
2.1 k enabled repos:
2.1 k /var/cache/yum/x86_64/7Server/rhel-7-server-rpms
0 disabled repos
0 untracked repos
37 other data:
37 /var/cache/yum/x86_64/7Server/timedhosts
2.1 k total
# ls -l /var/cache/yum/x86_64/7Server/rhel-7-server-rpms
total 4
drwxr-xr-x. 2 root root 6 Nov 1 10:17 gen
drwxr-xr-x. 2 root root 6 Nov 1 10:16 packages
-rw-r--r--. 1 root root 2159 Oct 29 23:31 productid
Oh, I just noticed a mistake in Comment 0:
"Actual results" talks about 3.7 k
"Additional information" talks about 2.1 k
The reason is that I ran the --verbose command on a different set of repos. Normally, the output in "Additional information" would look like this:
# yum clean all --verbose
[...]
Cleaning repos: rhel-7-server-rpms
Operating on /var/cache/yum/x86_64/7Server (see CLEAN OPTIONS in yum(8) for details)
Disk usage of /var/cache/yum/*/* after cleanup:
3.7 k enabled repos:
3.7 k /var/cache/yum/x86_64/7Server/rhel-7-server-rpms
0 disabled repos
0 untracked repos
37 other data:
37 /var/cache/yum/x86_64/7Server/timedhosts
3.7 k total
OK, you're actually right. I originally missed the fact that productid files are part of the standard metadata (listed in repomd.xml) and so are pulled regardless of the product-id plugin being active or not.
That said, it should be handled by yum itself. Removing the files on cleanup would probably pose an unnecessary risk of regressions, though, so we could as well just explicitly ignore these files when calculating the post-cleanup summary. In either case, I'm reassigning this to yum. Sorry for the noise.
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-2019:2286