Bug 1369258

Summary:	content hosts still see a repository that has been removed from the satellite
Product:	Red Hat Satellite	Reporter:	Kathryn Dixon <kdixon>
Component:	Repositories	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.1.9	CC:	bbuckingham, cdonnell, chrobert, shughes
Target Milestone:	Unspecified	Keywords:	PrioBumpGSS
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-12-15 19:41:25 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 Kathryn Dixon 2016-08-22 21:13:27 UTC

Description of problem:

After removing certain repositories from the satellite by unchecking them and then using the foreman-rake katello:delete_orphaned_content 

We gained back space in /var/lib/pulp and can no longer see the repos in the satellite webui ( there are no content views)

One repository that is "gone" in the webui, is still being accessible to clients. Even ones that we provision fresh.

The repo is rhel-7-server-supplementary-source-rpms

Version-Release number of selected component (if applicable):


How reproducible: 100% in customers environment.


Steps to Reproduce:
1. verify only repos syncd on the satellite are the ones we want
2. build a new client register it to the satellite
3. subscription-manager repos
4. the "ghost repo" rhel-7-server-supplementary-source-rpms will be there

Actual results:

# yum update fails due to the repo is not on the satellite anymore 404 error


Expected results:

this repo should not be available to clients.


Additional info: