Bug 1319312

Summary:	Hosts do no see all packages in a content view
Product:	Red Hat Satellite	Reporter:	Matthew Taylor <mataylor>
Component:	Content Management	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DEFERRED	QA Contact:	Katello QA List <katello-qa-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.1.7	CC:	bkearney, mataylor
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:	2017-04-12 18:31:04 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 Matthew Taylor 2016-03-18 19:14:45 UTC

Description of problem:

Hosts are not pulling the full repodata for repos in the content view the host is assigned.


This occurs for all host upgraded for 7.1 to 7.2 and for newly deployed hosts in both lab and production environments. 
Satellite and the Capsules use the same content view but are able to pull all the repodata.

How reproducible:

Always

Steps to Reproduce:

1. Sync rhel-7-server-rpms for rhel 7.2
2. Published a content view after the sync
3. Promoted the content view through two life cycles
4. Attempt to update host


Actual results:

Satellite shows the following under products:

Red Hat Enterprise Linux 7 Server RPMs x86_64 7.2	yum	Success 1 day ago	10348 Packages

After a yum clean all,  yum logs the following when pulling repo data:

rhel-7-server-rpms    10330/10330

There are no package filters for this repo configure on the content view.

The hosts are pulling content from a capsule. All content was synced to the capsules.


Expected results:

The host gets the latest repo data and is able to update with the latest packages


Additional info:

Comment 1 Bryan Kearney 2016-07-26 19:01:34 UTC

Moving 6.2 bugs out to sat-backlog.

Comment 4 Bryan Kearney 2017-04-12 18:31:04 UTC

Customer is saying this is no longer an issue. I am closing this out. If this is still being reported, please feel free to re-open with additional information. Thank you!