Bug 885782
Summary: | spacewalk-clone-by-date does not handle correctly invalid configuration file. | ||
---|---|---|---|
Product: | Red Hat Satellite 5 | Reporter: | Dimitar Yordanov <dyordano> |
Component: | Server | Assignee: | Stephen Herr <sherr> |
Status: | CLOSED ERRATA | QA Contact: | Red Hat Satellite QA List <satqe-list> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 550 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | spacewalk-utils-1.7.15-39-sat | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-01-18 13:47:17 UTC | Type: | Bug |
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: | 819027 |
Description
Dimitar Yordanov
2012-12-10 15:46:18 UTC
Since it is impossible for channel labels or package names to contain whitespace, why don't we simply strip the whitespace away from the values before we do anything else? If there is a more serious problem parsing the config file then we'll already throw an error for that, and if it's just a whitespace issue we can just fix it and move on. No need to throw another error for this. Committed to Spacewalk master: fa1ecf6982dbcda2e4bae938139bbe5032cfe468 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-2013-0167.html |