Bug 658210
Summary: | Yum RHN Plugin Exits '0' on Communication Failure | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Marcelo Moreira de Mello <mmello> |
Component: | rhnlib | Assignee: | Miroslav Suchý <msuchy> |
Status: | CLOSED DEFERRED | QA Contact: | Red Hat Satellite QA List <satqe-list> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.5 | CC: | cperry, james.antill, jhutar, mmello, msuchy, nbronson |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-03-14 16:40:22 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
Marcelo Moreira de Mello
2010-11-29 17:08:52 UTC
Current design of yum could not allow us to properly set exit code. I filed RFE for yum (bug 684859) and if it will be resolved (and back ported to RHEL5) you can reopen this BZ. But till then, there is nothing I can do. I think for this case you should just either raise PluginYumExit() or even raise Errors.RepoError. I do not think I want to raise Exit Exception and for sure not in prep phase. This is not fatal event. If you have some local repo, you can proceed without problem and upgrade your system. I just want to give user ability that this plugin had some serious problem. And writing to stdout seems to be out of question. |