Bug 752191
| Summary: | Promoted KS tree not working | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Steve Reichard <sreichar> |
| Component: | Content Management | Assignee: | Katello Bug Bin <katello-bugs> |
| Status: | CLOSED ERRATA | QA Contact: | Garik Khachikyan <gkhachik> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0.0 | CC: | cpelland, gkhachik, hbrock, imcleod, jrist, lzap, mkoci, pkilambi, scollier, tsanders |
| Target Milestone: | Unspecified | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-05-15 18:46:36 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: | 747354 | ||
|
Description
Steve Reichard
2011-11-08 19:19:33 UTC
The issue here is not treeinfo, pulp sets the treeinfo file at the top level url. The issue is how the repo associate was doing symlinks. There is a bug in pulp i noticed and fixed today where the symlink logic was missing the sub directory and since you're doing promote in katello it uses the same logic from pulp. This should make it into next pulp qe build. I'll update this bug with the fixed version of pulp and you can validate it. Putting this ON_QA. Note: Please test it against next pulp qa build or CR. ^^^ Prad, can you tell us how to test this - I am guessing checking for some symlinks somewhere in pulp after a promotion of something? This BZ is a disaster. There is no git commit hash,no indication of what version of Pulp the fix lands in, and no information on how to verify the fix. Pulp dev needs to provide this information. I'm moving it back to ASSIGNED and resetting to beta 6. Hmm... dev should not be moving to on_qa at this point in the workflow, only the errata tool should do that. I'm going to move this to modified, please make sure the issue is attached to the correct advisory and the BZ state will be handled automatically. 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/RHEA-2012-0666.html |