Bug 630599
| Summary: | after channel sync I do not see packages in erratas | ||
|---|---|---|---|
| Product: | Red Hat Satellite 5 | Reporter: | Jan Hutař <jhutar> |
| Component: | Satellite Synchronization | Assignee: | Michael Mráka <mmraka> |
| Status: | CLOSED DUPLICATE | QA Contact: | Red Hat Satellite QA List <satqe-list> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 540 | CC: | cperry, jpazdziora |
| 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: | 2010-09-10 09:01:49 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: | 487678 | ||
Re-tested with Satellite-5.4.0-RHEL5-re20100903.1 synced from Errata.stage and issue is still there. Maybe the same as bug 627566? *** This bug has been marked as a duplicate of bug 627566 *** |
Description of problem: I have synced rhel-i386-as-4 channel (from Errata.stage and then re-synced from Prod to be sure), but I still can not see packages in erratas. Version-Release number of selected component (if applicable): Galactica: Satellite-5.4.0-RHEL5-re20100827.0-x86_64-embedded-oracle.iso spacewalk-backend-tools-1.2.8-1.el5sat How reproducible: on 1 satellite, always Steps to Reproduce: 1. # satellite-sync -c rhel-i386-as-4 2. On WebUI go to: Channels -> Red Hat Enterprise Linux AS (v. 4 for 32-bit x86) -> Errata -> click on random one -> Packages Actual results: Packages Red Hat Enterprise Linux AS (v. 4 for 32-bit x86) (none) I do not see these packages even using XMLRPC call client.errata.listPackages(key, e['advisory_name']). Expected results: There should be some packages Additional info: This might be same issue as bug 630595, just a different symptom.