1. Proposed title of this feature request
Request to add a smart check for "yum clean all" command (in RHEL 7.4) for the disabled repositories before displaying warning message.
2. What is the nature and description of the request?
In RHEL 7.4 # yum clean all command is shows a warning message "Maybe you want: rm -rf /var/cache/yum, to also free up space taken by orphaned data from disabled or removed repos" every time even if there are no disabled repos consuming disk space for its repodata. This change was implemented as a part of bugzilla : 1357083
4. Why does the customer need this? (List the business requirements here)
The warning message is not user friendly for normal users (developers), users get confused with the warning. This warning is displayed even if the system is not registered to the customer portal and using only local repositories.
5. How would the customer like to achieve this? (List the functional requirements here)
# yum clean all command should check the enabled vs disabled repositories and if there is significant amount of space consumed by the disabled repositories then only the warning message should be displayed on the console to clean the disk space consumed by the disabled repositories.
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Running # yum clean all command should smartly check the disk space consumed by the disabled repositories and show warning message only if there is significant amount of space consumed by the disabled repositories.
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
- Issue needs to be resolved as soon as possible
9. Is the sales team involved in this request and do they have any additional input?
10. List any affected packages or components.
11. Would the customer be able to assist in testing this functionality if implemented?
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.