Bug 758221
Summary: | Spacewalk-repo-sync fails with a Traceback. | ||
---|---|---|---|
Product: | Red Hat Satellite 5 | Reporter: | Dimitar Yordanov <dyordano> |
Component: | Server | Assignee: | Jan Pazdziora (Red Hat) <jpazdziora> |
Status: | CLOSED ERRATA | QA Contact: | Red Hat Satellite QA List <satqe-list> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 541 | CC: | cperry, mmraka, slukasik |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-04-10 07:28:11 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: | |||
Bug Depends On: | |||
Bug Blocks: | 677498 |
Description
Dimitar Yordanov
2011-11-29 15:06:11 UTC
(In reply to comment #0) > Expected results: > spacewalk-repo-sync has the following behavior: > 1. Log a message that one RPM package is missing. > 2. Sync the rest of the RPM packages and claim SUCCESS. I don't agree with this expected behaviour. If one file is missing unavailable, dependencies might be broken among the rest of the packages. Reporting success would be ill-advised. I agree the we should not traceback, but the spacewlk-repo-sync definitely should not claim success. (In reply to comment #1) > (In reply to comment #0) > > Expected results: > > spacewalk-repo-sync has the following behavior: > > 1. Log a message that one RPM package is missing. > > 2. Sync the rest of the RPM packages and claim SUCCESS. > > I don't agree with this expected behaviour. If one file is missing unavailable, > dependencies might be broken among the rest of the packages. Reporting success > would be ill-advised. I agree the we should not traceback, but the > spacewlk-repo-sync definitely should not claim success. Yes, claim SUCCESS was not very bright idea. I would like to suggest the following behavior: 1. Sync all available RPM packages. 2. Log all packages that are missing 3. Exit code equals to the number of RPM packages that are missing. Dimi (In reply to comment #2) > 3. Exit code equals to the number of RPM packages that are missing. Can't do. Exit code is eight bits. (In reply to comment #3) > (In reply to comment #2) > > 3. Exit code equals to the number of RPM packages that are missing. > > Can't do. Exit code is eight bits. Possible decision is exit code 255 to be returned if 255 or more packages are missing. This bug has been fixed as a side effect of bug 769176 which went live as a part of http://rhn.redhat.com/errata/RHBA-2012-0457.html. |