Red Hat Bugzilla – Bug 644393
RFE: Don't return error if --disablerepo doesn't exist
Last modified: 2014-01-21 01:19:39 EST
Description of problem:
Yum will return an error if a repository listed in the --disablerepo switch doesn't exist. For example:
yum update --disablerepo="no-exist"
Loaded plugins: rhnplugin, security
Error getting repository data for no-exist, repository not found
This is a RFE to allow yum to continue if the repository is not existing.
Version-Release number of selected component (if applicable):
The impact of this bug is that some automated test cases require special handling for RHEL5/6 where repo names are different.
We should probably fix this upstream, but I'm less sure about how important it is in RHEL-5 ... and there is a work around:
yum update --disablerepo="no-exist" == fail
yum update --disablerepo="no-exist," == works
...due to the fact that we allow:
yum update --disablerepo="exists,no-exist"
so I'm torn on this one:
on one side:
- If we don't bail out and the user has just fat-fingered a repo name then they could get unanticipated results and cause any number of other problems
- If we do bail out then the user just has to correct the command line for the right repo name and start again.
I am leaning on the side of caution and I'd rather bail out.
If the impact is that rhel5 and rhel6 require different testing then I'm inclined to say 'yes, that's true, they are different.'
Is there an impact to our users/customers?
(In reply to comment #3)
> Is there an impact to our users/customers?
Customers - likely not. For QE it makes live a bit easier but anyway we did a work around already.