Bug 1313026

Summary: Satellite 6: EPEL repositories not syncing errata's
Product: Red Hat Satellite Reporter: achadha
Component: RepositoriesAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED CURRENTRELEASE QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1.7CC: arahaman, bkearney, chrobert, cpatters, kshirsal, riehecky
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-04 21:07:01 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:

Description achadha 2016-02-29 18:39:40 UTC
Description of problem:

EPEL repositories not syncing errata's. However, the sync is completed successfully and packages are synced. But it do not sync's errata and show "0 Errata"

Version-Release number of selected component (if applicable):
Satellite 6.x

How reproducible:


Steps to Reproduce:
1. Create a product
2. Add the details to create a EPEL repository(URL, name. etc)
3. Sync the repository

Actual results:
Sync gets completed successfully with the packages synced, but errata shows as 0.

Expected results:
Errata's should also be synced.

Additional info:
Used the below different URL to sync the EPEL repository on 3 different satellite with the same result, errata shows as 0.

http://mirrors.rit.edu/epel/7/x86_64/
https://dl.fedoraproject.org/pub/epel/6/x86_64/
http://mirrors.kernel.org/fedora-epel/6Server/x86_64/
http://mirrors.kernel.org/fedora-epel/7/x86_64/

However, the same EPEL repository on Satellite 5 shows the errata list and information.

Comment 1 Bryan Kearney 2016-07-26 19:03:09 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 3 Bryan Kearney 2016-09-12 16:11:22 UTC
There were several fixes around EPEL in 6.2. Can you confirm if the customer is still seeing this issue?

Comment 6 Bryan Kearney 2016-10-04 21:07:01 UTC
Per he comemnts in this bug, this bug has been addressed in Satellite 6.2. I am closing this out as CURRENT_RELEASE. If this is not acceptable, please feel free to re-open with additional information.