Bug 669313

Summary: syncing the rhel-i386-server-5 fails due to missing errata 10617
Product: [Retired] Red Hat Network Reporter: edoardo linington <eliningt>
Component: RHN/ChannelsAssignee: rhn-dev-list
Status: CLOSED CURRENTRELEASE QA Contact: Red Hat Network Quality Assurance <rhn-qa-list>
Severity: high Docs Contact:
Priority: low    
Version: RHN StableCC: nbronson, sskracic
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-24 11:46:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description edoardo linington 2011-01-13 10:13:50 UTC
when syncing rhel-i386-server-5 on a satellite 5.3, we have a failure with

Error Message:
    No such erratum rhn-erratum-10617

Error Class Code: 3005
Error Class Info: Unable to retrieve erratum
Explanation: 
     An error has occurred while processing your request. If this problem
     persists please enter a bug report at bugzilla.redhat.com.
     If you choose to submit the bug report, please be sure to include
     details of what you were trying to do when this error occurred and
     details on how to reproduce this problem.



Version-Release number of selected component (if applicable):
affects for sure satellite 5.3 ; affects rhel-i386-server-5 but may affect all
server5 channels. doesn't affect childs.

How reproducible:
always, even after clearing with

#rm /var/cache/rhn/*/* -rf

Steps to Reproduce:
0. rm /var/cache/rhn/*/* -rf
1. satellite-sync -c rhel-i386-server-5


Actual results:
SYNC ERROR:

(Check logs/email for potentially more detail)


Error Message:
    No such erratum rhn-erratum-10617

Error Class Code: 3005
Error Class Info: Unable to retrieve erratum
Explanation: 
     An error has occurred while processing your request. If this problem
     persists please enter a bug report at bugzilla.redhat.com.
     If you choose to submit the bug report, please be sure to include
     details of what you were trying to do when this error occurred and
     details on how to reproduce this problem.


Expected results:
syncronization should work

Comment 1 Sebastian Skracic 2011-02-24 11:46:24 UTC
Fixed with the help from CIS.  Please reopen if the issue persists.