Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 514797

Summary:	stage repomd.xml regeneration doesn't play nice with RHEL-QE and TPS
Product:	[Retired] Red Hat Network	Reporter:	Chris Duryee <cduryee>
Component:	RHN/Backend	Assignee:	Bryan Kearney <bkearney>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Red Hat Network Quality Assurance <rhn-qa-list>
Severity:	medium	Docs Contact:
Priority:	low
Version:	RHN Stable	CC:	acarter, dhughes, rhn-bugs
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:	Rally DE1
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-02-09 18:11:03 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:
Bug Depends On:
Bug Blocks:	519741

Description Chris Duryee 2009-07-30 19:55:10 UTC

Description of problem:

In the stage environment, repodata is regenerated using the same method that we used to use in prod. However, during heavy RHEL testing, the following scenario plays out:

* someone pushes new packages to stage channels
* TPS gets run, and hammers XMLRPC
* stage xmlservers attempt to regenerate repodata, and become overwhelmed with requests from TPS
* stage xmlservers become unresponsive
* RHEL-QE complains to Eng Support that stage is down

Ideally, we could use the new repodata regen process in stage, but have some kind of email or trigger that tells TPS when it can run.