Bug 150598

Summary:	2.1 Beta Channels need to be cleared
Product:	[Retired] Red Hat Network	Reporter:	John Flanagan <flanagan>
Component:	RHN/Channels	Assignee:	Chris MacLeod <cmacleod>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	RHN Devel	CC:	rhn-bugs
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-03-22 17:05:44 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description John Flanagan 2005-03-08 20:36:00 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040922

Description of problem:
The existing RHEL2.1 beta channels should be cleared of content so that we can pus the U7 beta packages.

Channel labels to be cleared:

rhel-i386-as-2.1-beta
rhel-i386-es-2.1-beta
rhel-i386-ws-2.1-beta
rhel-ia64-as-2.1-beta
rhel-ia64-ws-2.1-beta


Thanks!

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


How reproducible:
Always

Steps to Reproduce:
1. Look at the channels.
2. Mimicing the "strange Italian Guy" from Eurotrip, mutter, "oh, me scussi"
3. Ask that the packages be removed.  Stay away from the absinthe.
  

Additional info:

Comment 1 Chris MacLeod 2005-03-08 21:16:53 UTC

cleared in qa.

This will require ops intervention to take place in production.

Comment 2 Chris MacLeod 2005-03-18 21:03:25 UTC

the channel clear in production is blocking on purging the existing packages
from the recycled org.  At initial count there were 13K packages in the recycled
org some of which were causing a contraint violation with the new packages we
were intending to delete.  Prod ops is currently running the purge.  Due to the
number of packages and the potential locking of tables this process can cause
it's being run fairly conservatively.  This mean it'll take a while to run. 
Probably well into tomorrow to be honest.