Bug 735333

Summary:	'yum clean' gives a wrong impression
Product:	Red Hat Enterprise Linux 6	Reporter:	Šimon Lukašík <slukasik>
Component:	yum	Assignee:	James Antill <james.antill>
Status:	CLOSED ERRATA	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	low	Docs Contact:
Priority:	low
Version:	6.1	CC:	ksrot, pknirsch, zpavlas
Target Milestone:	rc
Target Release:	6.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	828690 (view as bug list)		Environment:
Last Closed:	2012-06-20 13:53:41 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Šimon Lukašík 2011-09-02 11:48:56 UTC

Description of problem:
The command 'yum clean' is considered too ambiguous by yum to commit
any action. The error message is emitted.

However the rest of the output of Yum as whole might give a wrong
impression that the appropriate actions are made.

Version-Release number of selected component (if applicable):
yum-3.2.29-17.el6.noarch

How reproducible:
Deterministic

Steps to Reproduce:
1. Have some repositories enabled
2. yum clean
3.
  
Actual results:
# yum clean 
Loaded plugins: product-id, rhnplugin, subscription-manager
Updating Red Hat repositories.
Error: clean requires an option: headers, packages, metadata, dbcache, plugins, expire-cache, rpmdb, all
Cleaning repos: beaker rhel-x86_64-server-6
# echo $?
0

Expected results:
# yum clean 
Loaded plugins: product-id, rhnplugin, subscription-manager
Updating Red Hat repositories.
Error: clean requires an option: headers, packages, metadata, dbcache, plugins, expire-cache, rpmdb, all
# echo $?
1

Additional info:

Comment 7 errata-xmlrpc 2012-06-20 13:53:41 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.

http://rhn.redhat.com/errata/RHBA-2012-0857.html