Bug 1324475

Summary:	RHEVM 3.6 repo has the errata but no updates packages when the channel is synced on Satellite 6 server.
Product:	Red Hat Satellite	Reporter:	Kamudini Gazdikova <kshirsal>
Component:	Content Management	Assignee:	Tomas Strachota <tstrachota>
Status:	CLOSED NOTABUG	QA Contact:	Katello QA List <katello-qa-list>
Severity:	high	Docs Contact:
Priority:	high
Version:	Unspecified	CC:	bkearney, ekin.meroglu, kshirsal, tstrachota
Target Milestone:	Unspecified
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-04-07 09:10:12 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:

Description Kamudini Gazdikova 2016-04-06 12:15:38 UTC

Description of problem:

RHEVM 3.6 repositories has the errata for RHBA-2016:0583 but no updated packages when the channel is synced on Satellite server.

Version-Release number of selected component (if applicable):
Red Hat Satellite v. 6.1
CDN

How reproducible:
Every-time

Steps to Reproduce:

- Sync the channel 'Red Hat Enterprise Virtualization Manager 3.6 RPMs x86_64'
it marks as "No new packages" 

- # yum list on the registered on the client system  mentions the old version, even tough the latest content is synced for the repository on the Satellite server.
~~~snip~~~
yum list rhevm
Loaded plugins: package_upload, product-id, security, subscription-manager
Repository rhel-source is listed more than once in the configuration
Repository rhel-source-beta is listed more than once in the configuration
rhel-6-server-rhevm-3.6-rpms                                                                                     | 2.3 kB     00:00     
rhel-6-server-rpms                                                                                               | 2.1 kB     00:00     
rhel-6-server-satellite-tools-6.1-rpms                                                                           | 2.1 kB     00:00     
Available Packages
rhevm.noarch                                        3.6.3.4-0.1.el6                                         rhel-6-server-rhevm-3.6-rpms
~~~snip~~~

- Systems registered with Satellite 5/ RHN Classic are able to fetch the latest package updates in
RHBA-2016:0583

Actual results:
Syncing the channel 'Red Hat Enterprise Virtualization Manager 3.6 RPMs x86_64' not fetching the latest errata updates.

Expected results:
Syncing should work and get the channel updated with the latest content.

Comment 1 Tomas Strachota 2016-04-06 13:00:57 UTC

I suspect the problem is not on Satellite side:

I checked the CDN content and metadata referenced in repomd.xml. updateinfo.xml.gz for the repo does contain the errata, but affected packages aren't listed in filelists.xml.gz.

I'll reach content services and make sure the repository is correct.

Comment 3 Tomas Strachota 2016-04-07 09:10:12 UTC

The issue was resolved by re-generating metadata in the CDN repo.
I'm closing this bug.

Comment 4 Bryan Kearney 2016-04-07 12:03:50 UTC

Kumudini:

Can you please have the customer re-test and let us know if this did not fix it?

Thanks!

-- bk

Comment 5 Kamudini Gazdikova 2016-04-08 09:07:33 UTC

Hello Bryan,

Yes it is confirmed that it fixes the issue.

However they have a similar issue in the hypervisor channel:

The Errata was published on 04.04.16, and the updated package is rhev-hypervisor7-7.2-20160328.0.el6ev.noarch.rpm

https://access.redhat.com/errata/product/150/ver=/rhel---6/x86_64/RHBA-2016:0588

they have the repository sync'd, but neither the errata nor the package is present.

Additionally they have pointed out that that this is the fourth similar case they have opened since February as these CDN issues started to occur more frequently - so it seems there is a need for a enhancement on the repository / delivery side...

Comment 6 Bryan Kearney 2016-04-08 12:30:14 UTC

The RCM group is working to impprove the overall delivery of the bits. I will raise your concern to them, and put in a ticket for this case. I will copy you on the ticket so that you are kept aware of the progress.