Bug 552405
Summary: | kickstart fails on perl package | ||
---|---|---|---|
Product: | [Community] Spacewalk | Reporter: | Johnny Mirza <jmirza> |
Component: | Clients | Assignee: | Milan Zázrivec <mzazrivec> |
Status: | CLOSED DUPLICATE | QA Contact: | Red Hat Satellite QA List <satqe-list> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 0.7 | CC: | jpazdziora |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: |
staging
|
|
Last Closed: | 2011-09-02 12:36:28 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: | 723481 |
Description
Johnny Mirza
2010-01-04 22:02:00 UTC
I think I have resolved the issue and would like to confirm if it is a known bug in spacewalk. The perl-libwww-perl-5.805-1.1.1.noarch.rpm was in two spacewalk channels and I assume spacwalk would be able to pick any of the files as they were the same but this is not the case. After deleted one of the packages in one of the channels the kickstart build completed successfully and didn't dont warn or error for the perl package. I am not sure if this is a satellite known fact or a bug. thanks Mass-moving to space13. We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5. We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5. Aligning under space16. (In reply to comment #1) > I think I have resolved the issue and would like to confirm if it is a known > bug in spacewalk. > > The perl-libwww-perl-5.805-1.1.1.noarch.rpm was in two spacewalk channels and I > assume spacwalk would be able to pick any of the files as they were the same > but this is not the case. After deleted one of the packages in one of the > channels the kickstart build completed successfully and didn't dont warn or > error for the perl package. > > I am not sure if this is a satellite known fact or a bug. This was fixed by commit a342b5f3f447811989b3e31f9104e5c004214cc8. *** This bug has been marked as a duplicate of bug 610134 *** |